SDK you're using (please complete the following information):
Version [1.6.0]
Describe the bug
Before this update when sending a BATCH of invoices using CreateInvoicesAsync the returning result (list of invoices) were in the order that they were sent (matching the source list order).
It would now appear that the returning result is in date order which means I have no way of knowing which invoice matches what was sent. Is it possible to revert this back to how it was in previous versions as I am now unable to match invoice posting with the source data.
To Reproduce
Steps to reproduce the behavior:
Batch send invoices in a random date order and the posted results return in date order and not the original sent order.
Expected behavior
Batch posted invoices return results in the order that they were sent.
If there was a way of knowing the GUID of an invoice before it was posted I could use this but this appears to only get created when the posting is done which by then the result order is lost.
SDK you're using (please complete the following information):
Describe the bug Before this update when sending a BATCH of invoices using CreateInvoicesAsync the returning result (list of invoices) were in the order that they were sent (matching the source list order).
It would now appear that the returning result is in date order which means I have no way of knowing which invoice matches what was sent. Is it possible to revert this back to how it was in previous versions as I am now unable to match invoice posting with the source data.
To Reproduce Steps to reproduce the behavior: Batch send invoices in a random date order and the posted results return in date order and not the original sent order.
Expected behavior Batch posted invoices return results in the order that they were sent.
If there was a way of knowing the GUID of an invoice before it was posted I could use this but this appears to only get created when the posting is done which by then the result order is lost.