This is not a known issue. It is possible that the OData cache is being confused with the caches for Exact Online.
The premise of Invantive Cloud is real-time processing. At various levels, caches (possibly) exist to increase processing speed:
- Platform cache (Exact Online); for
SystemDivisionswhen logging in to Exact Online, this is normally updated automatically if there is a change in the number. Controllable via statements such asset use-http-disk-cache@ALIASandset use-http-memory-cache@ALIAS(see Invantive UniversalSQL - Invantive Product Documentation). - Result set cache: currently only for XML.
- Application cache: only for
*Incrementaltables on Exact Online, Freshdesk and Fresh Service. - Response cache (only for OData): as set with the database on Invantive Cloud and partly controlled via Cache headers (see Realtime OLTP verzoeken via OData4 voor Power Apps en Power BI).
Is it possible to add a reproduction scenario?
For precise control over the operation, it is advisable not to use the OData connection, but to connect directly for instance via ADO.NET, C#, or the TDS protocol (Invantive UniversalSQL Server, optionally on-premises) with Invantive Credentials Server.