Dataverse Refresh rate

[RogerCP66]

I had a question about Dataverse I was hoping someone could help with. It is a project that my team is working on for external users via Power PAges to provide details that are than managed via an internal Power App. We have a set of power pages forms (External) to Dataverse, and then a Power App (Internal) that is a grid view that manages the (confirm/approval process). Actions on either side are not being reflected automatically. Is there  a way to fix this?

Any way to refresh data via power apps or power pages via a manual option or by using Power Automate?

[dpoggemann]

Hi @RogerCP66 ,

Are you talking refresh on a view or grid?  The data is stored live to Dataverse if entered in forms in Power Pages.  Can you provide more details on what is not reflecting immediately as I might be misunderstanding.

[RogerCP66]

Hi @dpoggemann Im talking about how quickly the data is accessible. We are using Power Pages to submit a request on the external side and on the internal side we have a Power App that manages the request. The internal user may approve, deny, or need more information regarding the initial request. This process is somewhat time sensitive but we are finding that changes on either side in Power Pages or Power Apps are quite delayed and my understanding is this may be due to dataverse. Hope that clarifies the problem

[dpoggemann]

Hi @RogerCP66,

If you are using a form on a Power Page and enter the field values, click save, it is directly storing this information to Dataverse.  Are you using a model-driven application on the backend or are you using a Canvas app that is querying the data?  If a canvas app it might be something with how you are retrieving the data?  

As a test, submit from Power Pages and check in Maker portal, it should be in Dataverse immediately after submission.

[RogerCP66]

Hi @dpoggemann on the initial submission it is quick. But having the review and approval that is competed on the internal side can take quite a while to then show up again on the Power Pages side for the external user. Also it is a canvas app.

I really appreciate your help.

[dpoggemann]

Hi @RogerCP66 ,

You might be dealing with caching (https://learn.microsoft.com/en-us/power-apps/maker/portals/admin/clear-server-side-cache).  See the FAQ details on this page for how caching affects Power Pages.

[Fubar · Accepted solution]

Data that is created/modified in dataverse from an another interface is not pushed in real time to the Portal Cache.  The primary record that is created/updated from the Portal is available in real-time - secondary records (e.g. a plugin that triggers on create of the primary record that creates a related record) are not pushed to the cache in real-time.

the SLA for the push to the cache is 15 mins but usually occurs within a couple of minutes.

The only way to surface such records is to break the cache (by including conditions on the query that will make the query have to go to dataverse and not the cache e.g. include createdon equals now down to seconds) which can be done if making the queries yourself and not using the standard Lists etc.  = breaking the cache is not recommended

Also, this is by design by Microsoft - in the old days it was more real-time and in the old old days you could push the data from dataverse, 

[RogerCP66]

Hi @Fubar really appreciate the insight. This is helpful.

Do you know if this is something that will likely be improved in updates to Power Pages?

[Fubar]

@RogerCP66 I don't know for sure, but over time they have moved away from more real-time so suspect it won't get any better.

[dcharpentier]

Hi @Fubar, all, 
Related question : my custom table doesn't refresh at all in PowerApps, even though the dataflow is refreshed every hour (FYI it uses a Power Query to a web-based ERP).

What am I missing ?