Setting field `sale_id` on Ticket results in error
Hello,
I'm trying to link a sale to a ticket, using this endpoint:
PATCH https://online3.superoffice.com/Custxxx/api/v1/Ticket/123 body=[{
"op":"replace", "path":"sale_id", "value":"[I:456]"}]Bad Request — There is no property named "sale_id" on type TicketEntity.Looking in the documentation, at the Ticket table, I see that
sale_id is listed (source https://docs.superoffice.com/en/database/tables/ticket.html)What am I doing wrong?
Alles Antwoorden (4)
Hi,
The patching is based on the Services definition of entities, not the database definition, So if you look at the TicketEntity properties of the service definition, you will see that 'Sale' is a seperate property, The sale property/definition contains a property 'SaleId', that is the one you want.
So your patch operation should look like this
PATCH https://online3.superoffice.com/Custxxx/api/v1/Ticket/123 body=[{
"op":"replace", "path":"Sale/SaleId", "value":"[I:456]"}]Getting a follow-up error from this request: FetchError: Bad Request β Could not convert string to integer: [I:3300940].
The body that we sent to SuperOffice was: [{
"op":"replace",
"path":"Sale/SaleId",
"value":"[I:3300923]"
}]
We do use the [I:123] notation in other places without problems. And the integer type should not have probles at 3300923
π€ What could be the issue here?
PS: It's rather unrelated to my original question. Would you like me to post it separately?