Answered

How to fix caching issue in Power Pages Site?

(2) Share

Report

Posted on by rbn_neu

Hi Folks,

In my power pages site I'm retrieving data from dataverse using Power Pages Web API. Everything's working fine except when I update the data in dataverse outside the power pages (via a Model Driven app), the change is not getting affected immediately when I open the site. It takes around 1 to 5 min to get the update reflected. For example I want to navigate the user to different pages based on data, which does not happen as expected shortly after the data is updated.

Any thoughts on how to fix this?

Thanks,

Robin

Categories:

Design & build

All responses (3)

Answers (1)

Sort by

Suggested answer

Jon Unzueta 1,836 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@rbn_neu

When calling the Web API from JavaScript, ensure you're preventing browser and server caching:

fetch("/_api/table_name(guid)", {

  method: "GET",

  headers: {

    "Cache-Control": "no-cache",

    "Accept": "application/json"

  }

})

This content may have been partially translated, structured, or generated with Copilot 🏷️ Tag me if you have any further questions or if the issue persists. ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems. ❤️ Give it a Like if you found the approach useful in any way.
rbn_neu 46 on at

Like
a
(0)

Report
Copy link

Link copied!

@Jon Unzueta

Ya this is already in place but still it takes a few minutes before the database changes done outside power pages site is reflected on the power pages site.
Verified answer

Fubar 17 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
The caching you describe is by design by Microsoft (the SLA is actually 15 mins for updates from Dataverse to reflect on the portal, but usuall occurs within a few minutes).

If you are using the Portals Web API, or where you may be using fetchxml in Liquid the workaround is to add a condition to your query that will make the query relatively unique but always return true (true so it doesn't impact the rest of your query) - as an example this can be done by adding a condition based on the Created On date where it is less than the date-time now (formatted down to seconds).

e.g. a condition in Liquid

<condition attribute="createdon" operator="on-or-before" value='{{ now | date: "yyyy-MM-dd HH:mm:ss" }}' />