SystemDivisions shows new records later — can we force that?

Questions (nl)
,
1

Situation: In Exact Online, new administrations are added to the app authorisation. The user sees them immediately in Exact Online itself. In Invantive Bridge Online (table SystemDivisions), they sometimes only appear after a while on our side. I think this matches that 1-hour cache if the number of partitions changes (and 10 hours if only metadata changes)?

We already force our own cache to refresh, but of course, that doesn’t help if SystemDivisions on the Invantive Bridge Online side is still outdated.

Questions:

  1. Is that 1 hour / 10 hours still the case?
  2. Is there a way from Bridge Online / OData to really fetch SystemDivisions again (without manually clicking “reset cache” in the Cloud)?
  3. Does re-authenticating / starting a new session help, or does it make no difference?

We want to be able to give our clients transparent information in our UI (“can take up to an hour”), but ideally also provide a button that really helps if such a button exists.

2

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 SystemDivisions when logging in to Exact Online, this is normally updated automatically if there is a change in the number. Controllable via statements such as set use-http-disk-cache@ALIAS and set use-http-memory-cache@ALIAS (see Invantive UniversalSQL - Invantive Product Documentation).
  • Result set cache: currently only for XML.
  • Application cache: only for *Incremental tables 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.

6

This question has been automatically closed after 1 week of inactivity. The last given answer has been marked as the solution.

Please post a new question in a separate topic if the issue reoccurs. In the new question, please include a link to this topic by pasting its URL in the text.