Unanswered

Data refresh issue Custom Page in Model-driven app

(1) Share

Report

Posted on by TomPwrPltfrm

I'm experiencing an issue where my Custom Page doesn't load the latest data. The Custom Page is embedded in a Model-driven App. What I have tested:

When I make changes to my data first and then open the custom page for the first time then everything works fine.
If I open the custom page first, then make changes to the data, then go back to the custom page it takes 20-30 seconds for the latest changes to be loaded into the page. Even if I use the Refresh function in Power Fx it doesn't update the data directly. Only after those 20-30 seconds.
If I refresh my page in the browser then the changed data is loaded into the custom page immediately.
For testing purposes, I have rebuilt my custom page in a Canvas App and there I don't have this issue. The data in the Canvas App is refreshed without delay when I use the Refresh function in Power Fx.

Based on my testing results it seems that the data from Dataverse is cached into the custom page when you open it. When I change the data in Dataverse, it takes 20-30 seconds for the cache to pick up the changes. It seems that the Power Fx Refresh function refreshes the cached data and not the actual data source.

For obvious reasons, this is not a workable situation. Did anyone experience the same issue? Is it intended to work like this? Or is there a way to work around this issue?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

tshelbourn 19 on at

Like (0)

Report

just started using Custom Pages more and getting the same issue. Did you find any answers? Doesn't seem to be an issue using a Canvas App.

Was this reply helpful? Yes No
TomPwrPltfrm 6 on at

Like (1)

Report

I have been in contact with Microsoft support for the last months and it turns out this is by design. They have a mechanism in place that caches API requests to Dataverse for about 20 seconds. This only applies to custom pages and not to Canvas Apps. For testing purposes, you can add this flag to the URL of your custom page while you play it in the model-driven app and that turns off the caching mechanism: &flags=FCB.MdlResponseCache=false. If you want, you can open a support ticket with Microsoft and request them to turn off this caching mechanism for specific Dataverse environment(s).

Was this reply helpful? Yes No
tshelbourn 19 on at

Like (0)

Report

Well this is inline with what I'm seeing but does not make me happy. I will get a hold of them. Thx for getting back to me.

Was this reply helpful? Yes No