ODP_Serialization_Error when calling Service Quotation
Hi All,
We are receiveing the below error when pulling Service Quotation API. It gets to Quote D193 Rev 1 and then this error appears
"<ERROR> {"error": {"code":"ODP_SERIALIZATION_ERROR", "message":"Error while serializing contents." } }</ERROR>
If we call just Quote D193 we do not get the error. We have checked the Quote in IEE and it is no different to the previous Quote in the API Call as far as Data goes.
How can we debug this? Developer has used Postman but it does not detail which field or indicate if there is a character error.
Thanks,
Lisa
Page 1 / 1
If you look for the error it is mostly two things:
You should add these things to your header
Make sure to encode your Etag correctly (you have to escape the \ .
@lisa.gilesAB could you show what you currently push to the system>? How your full api call looks like?
Thanks @kvbe
This is what the Developer has sent me for the segment with the error. He says we don’t do any of the above as that was not how IFS set this up for us.
{"@odata.etag":"W/\"Vy8iQUFBYlNjQUFmQUFGdklOQUFIOjE0Ig==\"","luname":"ServiceQuotation","keyref":"QUOTATION_NO=D193^QUOTATION_REV=1^","Objstate":"Closed","Objgrants":null,"QuotationNo":"D193","QuotationRev":1,"QuotationDesc":"OFF DMD WORK","QuotationRevText":null,"CustomerReference":null,"Printed":true,"InternalNotes":null,"ExternalNotes":"WO 96652","ReqReceiptDate":"2023-11-20","<ERROR>{"error":{"code":"ODP_SERIALIZATION_ERROR","message":"Error while serializing contents."}}</ERROR>
@kvbe The developer has also noted that it is failing when we try to read these values out of IFS. The API Read Call is failing when pulling ALL Quotations. If we API Read Call the Quote Referenced with the Error (D193 Rev1) we do not receive the same error.
We are only doing a READ Call not an Action, Update or Insert.
Thanks,
Hello Lisa,
If you have debugging privileges, could you please enable adding the query parameter "odata-debug=json" to the request? This will allow us to receive a response containing more detailed information about the error.
Hi @kosaladesilva
we tried that when we had someone on the call with us (not sure if IFS developer or 3rd party person) and yes we get lots of extra info, but nothing additional relating to the error message.
We are still experiencing this error and have not been able to find a way to debug and resolve.
Is there anything else we can try?
Any DB SQL Scripts that we can run to Debug the table?
