Page 1 of 1

Allow test readings values to be set without maintenance planner

Posted: Mon Jul 15, 2024 10:15 am
by taskerdev
It is of my understanding that test readings can be set without service levels on SimPRO's front-end. However, this is not reflected in the API, instead asking for a service level to be provided.

Attempting to set the service level within the request will also return a Slim Application Error (500).

Could this please be looked into? Thanks.

Re: Allow test readings values to be set without maintenance planner

Posted: Tue Jul 16, 2024 1:48 am
by SimproAPITeam
Definitely, we will raise a ticket to investigate this, can you share the endpoint you were using?

Thank you

Re: Allow test readings values to be set without maintenance planner

Posted: Tue Jul 16, 2024 4:04 pm
by taskerdev
I'm using the following API route:

/api/v1.0/companies/{companyID}/jobs/{jobID}/sections/{sectionID}/costCenters/{costCenterID}/workOrders/{workOrderID}/assets/{assetID}

https://developer.simprogroup.com/apido ... ba8e2a80cf

Re: Allow test readings values to be set without maintenance planner

Posted: Wed Jul 17, 2024 12:51 am
by SimproAPITeam
Thanks for the info,

Can you also PM us your build URL as well ?

Re: Allow test readings values to be set without maintenance planner

Posted: Wed Jul 31, 2024 8:39 am
by taskerdev
Are there any updates on this? This issue is preventing us from deploying a product for one of our customers.

Re: Allow test readings values to be set without maintenance planner

Posted: Thu Aug 01, 2024 6:06 am
by SimproAPITeam
Hi taskerdev,

We've responded to ur PM, you need to include the serviceLevel when you try to patch the testReadings.

Re: Allow test readings values to be set without maintenance planner

Posted: Thu Aug 01, 2024 9:01 am
by taskerdev
Hi,

As mentioned in my first message, I already tried to append the serviceLevel, which resulted in a 500 error. I have screenshots of this happening.

I just tried the same request again and the data went through, I assume that the bug has been fixed :) thanks!