Add More API Fields
Chauncey Hutter
Having a DoNotOrder field is necessary. Please consider adding this feature.
S
Steve Hobeck
Please elevate this. Supper important for our procurement process.
B
Ben Hobeck
Could we get an ETA on when the Do Not Order feature in the API will be implemented?
C
Cody Frisch
I'd like to also see the details of phased labor associated with the project in the integrations format. It's in Legacy but doesnt appear in Integrations (I'm assuming what I get from Send To - XML/JSON is the same as what gets sent to the cloud to then be made available).
Ideally it would be the hours of each sub-phase as calculated based on the difficulty and factors, the unit and total cost/price for each sub-phase, and the phase aggregate cost/price.
We need to be able to get the sub-phase data into an accounting system we use (that I can guarantee nobody else has.) so that actual labor can be billed against those labor items in the accounting system.
Eduardo Voloch
The fields currently available are:
"OrderStatus": null,
"OrderNumber": null,
"OrderedDate": null,
"OrderedDateTicks": 0,
"ExpectedDeliveryDate": null,
"ExpectedDeliveryDateTicks": 0,
We will add the Do Not Order
Service Orders and Tasks are being considered for development.