Rest API incorrect json format
Ibrahim Bashir
5-30-23
Operating system: Windows
Hello,

I am doing an integration with another software using REST API.

However, the response is incorrect when using the parameter updates_after

Here are examples how the response looks like
Without updates_after

{

"data": {

"@register": "INVc",

"@sequence": "12307035",

"@systemversion": "8.5.51.137",

"INVc": [{

"@register": "INVc",

"@sequence": "12307035",

"@url": "/api/1/INVc/0010211",

"Code": "0010211",

"Name": "VENTRIO Small Oval 8,0x12,0 cm 0010211 شبكة جراحية لعمليات فتاء منطقة



With updates_after:



{

"data": {


"@register": "INVc",

"@sequence": "12487206",

"@systemversion": "8.5.51.137"{

"@register": "INVc",

"@sequence": "12490406",

"@url": "/api/1/INVc/0117016",

"Code": "0117016",

"Name": "BARD SOFT MESH 30X30 LARGE 0117016 شبكة جراحية لعمليات فتاء منطقة الإربي",



Note: the response becomes correct when using filter parameter.

Is it a bug or there is something missing?

Version 8.5 2023.02.08

Thanks.

//Ibrahim
Gatis Jansons
6-1-23
Hello, Ibrahim.

Thank you for reporting this issue.
I have verified that it is indeed a bug, and not a setup issue.

As this part after @systemversion gets skipped:

,

"INVc": [


--------

I have reported this bug in our QA system and we will proceed with fixing it.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
Hello, Kindly please report the bug so that we can further investigate and resolve it. Thank you. Best regards, Benjamin...
11:31 3 May 2024
Hi, No changes should have been made that would increase client's HDB file. Please try to delete HANSA.HDB from client folder and reconnect to server and check if it will grow to 30MB again. ...
10:14 30 Apr 2024