Inaccurate data results when using lastModifiedDateTime

[MarcusHedlund]

Hi, We are experiencing a problem with data missing if its created to close to the time of the fetch request.

As an example,

We fetch Supplier invoices on a regular basis and we use the lastModifiedDateTime filter to only fetch new invoices since last time we checked. 

Sometimes we are not getting all of the invoices that are created since last fetch. 

Every time this has happened and we looked into this we noticed that the entities that are not fetched has a lastModifiedDateTime that is very near to the time of the request. Within 30 seconds every time.

A supplier invoice with "lastModifiedDateTime": "2024-12-09T07:59:45.327" was not fetched when doing the following request was done at "2024-12-09T08:00:05.244"

'https://integration.visma.net/API/controller/api/v1/supplierInvoice?lastModifiedDateTime=2024-12-09T07%3A30%3A00.000'

Other invoices with earlier lastModifiedDateTime was fetched in the same request.

This has happened on other endpoints/entities as well, for example JournalTransactions.

Is it to be expected that there could be differences between what lastModifiedDateTime says and whats actually fetched in a request when these two events happens close to each other?

I hope my explaination is understandable, if not im available to answer any questions.

Thanks

[Marten Voort]

Hi Marcus! Thx for your elaborate explanation. I have tested this and in my test with only a couple of purchase invoices I had no problems fetching very recently created invoices. I suspect when creating multiple transactions simultaneously, the system needs time to process and can only store the values once creation is successful. This is hard to prevent, because in case of an error or disruption of the service, a rollback must be performed. I have seen similar integrations that solved this using the MAX value of lastModifiedDateTime of the previous request result to perform the next request. Could this also apply for your process?