Increase of data transferred through GeneralLedgerBalance endpoint (8.25 version 15/09/2020 )

[#1]

Visma.net Financials API updates for version 8.25 (September 2020)

Increase of data transferred through GeneralLedgerBalance endpoint
Previously, the table containing balances did not have the LastModifiedDateTime column. To implement filtering by LastModifiedDateTime on GeneralLedgerBalance endpoint, the column from the Transactions table was used. However, this implementation might cause some issues.

Now there is the LastModifiedDateTime column in the Balances table and it is used in the API endpoint implementation.

This is not a breaking change. However, the integrators should expect an increase of transferred data first time they call the endpoint after release.
This behavior is determined by the new column. For the existing entries, the newly introduced column will be filled in with the current date and time.
There is no way to find out exactly when a balance was changed last time, so this approach is the only solution to ensure data integrity.

For example, the newly introduced column will be added during the upgrade on 15th of September 2020. For all lines the last modified date time will be set to '2020.09.08 hh:mm:ss'. Supposing an integrator had it's last synchronization on '2020.09.07 22:00:00', on next synchronization, after '2020.09.08 hh:mm:ss', the '2020.09.07 22:00:00' will be set as last modified date and time. Then there will be fetched all lines from database.
This will happen only on first synchronization after upgrade. On the next ones there will be set a last modified date and time greater than '2020.09.08 hh:mm:ss' and only really changed balances will be fetched.