Hi,
This issue was fixed by MYOB in the last weekend. But now it's back. I checked my ETL program and I have the same problem, NextPageLink is null.
I have a solution to this issued. I modified my ETL, if NextPageLink is null, my program assembles the NextPageLink for the next request by adding ?$top=400&$skip=xxxx to the end of the request URL, until the returned items is empty.
xxxx is the amount items that have already been processed.
My work arround is I forced the program to continue calling API until it reached page 30 which is not really ideal if we have tons of records, but i just found another issue
Endpoint Sale/Invoice/Item seems providing different number of Items than the record i requested. My program is always requesting for 1000 records and the Count value can see it but when i count the records on Items, it is not 1000(see item count.png)
But the Endpoint Sale/Invoice/Service is providing the correct record count(see service count.png)
Hi ,
In my program, only "Sale/Invoice/Item" has this issue, and in some responses , the number of actual returned items is not equal to the count value. But whole returned items is the same as before.
My comments aren't really contributing to any solution here but can't help but think the actual code and logic for this functionally behind the API is not that hard. It's just standard paging code. To set the link to null depending on if there are not any more records shouldn't be difficult. To build unit tests and mock it should be really simple as well. This is not a bug that should ever happen. Let alone happen twice. Am I missing something?
We're about to deploy our software to use the online API from a networked file and this is a little worrying. Are these sort of issues common? I've been using the .net SDK for a while now and haven't ever really had any issues.
My2cents
