More information about the operation of the incremental tables can be found at:
Up to 5 million booking entries can be processed per day from a cold start. Invantive SQL automatically builds the cache for larger environments, but generally, it’s not wise to process such large datasets via Invantive Cloud or incremental tables. It’s better to examine the behaviour and how more than 5 million records are obtained, and choose the appropriate approach for that.
If the Exact Online limit of 5,000 API calls is exceeded (or whatever limit has been commercially agreed with Exact Online), the engine supports spreading the initial load over the number of days set via the provider attribute max-age-sync-last-unused-days (event itgeneor255).
Please note:
- By default,
max-age-sync-last-unused-daysequals the number of days after which Exact Online removes delete transactions (previously set at 28-1) minus (arbitrarily chosen) 10. - The limit of 2 months was set from documentation in 2022 and is still the official value according to documentation. However, this was later lowered to 28 days in 2022 as the actual operation was found to be different. However, in 2026, there are persistent signals that Exact Online has now been operating with a much broader limit of 6 months as opposed to 28 days or 2 months. This discrepancy between documentation and actual behaviour is still under investigation (see Veel regels in SyncDeleted).
- Spreading the download over multiple days is of limited usefulness. Also, after an initial download, a full reconstruction is done if necessary to resolve known issues in Exact Online.
- Overall, the use of incremental tables is only recommended for administrations with a maximum of around 15 million rows. Choose other solutions like
*Bulktables with additional logic for larger environments; in practice, users are already aware that such numbers of rows lead to all sorts of challenges.