Portal Cache Nightmare

(1) Share

Report

Posted on by ID-24120023-0

Guys, I am at my wits end.

I have a record, in a custom table, that the user interacts with by clicking a button that makes an external http request to an Azure resource.

This Azure resource then updates the record state and returns a 200 OK.

My Javascript then refreshes the page... and still record shows in the old state for like 5 minutes even though the value has been updated in Dataverse.

Here is the kicker... I'm not using an OOB entity list or anything like that to render the record. I'm doing a straight up liquid fetchxml api call to Dataverse and it still returns the old value... even via API call from portal!

To summarize my question is: HOW DO I FORCE THE PORTAL TO RESPECT DATAVERSE UPDATES IN REAL TIME???

Categories:

WEB API

Portals

General

All responses (1)

Answers (0)

lbendlin 8,071 Super User 2025 Season 2 on at

Like (0)

Report

Portal Cache Nightmare

would it help to add a "&r=<random number>" to the fetch URL ?