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
