Answered

FetchXML returning old data

(0) Share

Report

Posted on by ShaneHubble

Is there a way for FetchXML to return the most up-to-date data from a table?

I've got a page that runs FetchXML when it loads. It looks at a Dataverse table and returns some specific values (employee number, a choice, department number). The page will display certain things depending on the value of the choice. This is done through liquid. The problem is, the choice can change when the user is on that page. If it does change and the page is reloaded, it's still grabbing the old choice value and not the new one. It shows the change in Dataverse though. It takes 5+ minutes for the FetchXML to get the most recent data.

Is this something that can be immediate?

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

Fubar 8,505 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Your queries will pull data from the Portals Cache which is why you see data where the data has been added/updated in Dataverse and not yet updated in the Cache (which takes a couple of minutes).
Note: It is not recommended by Microsoft to break the Cache, but you can if you are querying the data yourself (you can't if using a standard view), what you do is add a condition into your fetchxml that includes date-time down to seconds (e.g. createdon is less than or equal to today). Basically this makes your query a bit more unique (except for another user making the same query in the same second) and so will pull the data from Dataverse.

(I don't have it at hand, but you will find this has been answered with an example in the past)

Was this reply helpful? Yes No
ShaneHubble 34 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for the suggestion. Adding
<condition attribute='modifiedon' operator='on-or-before' value='{{ 'now' | date:'MM/dd/yyyy HH:mm:ss' }}'/>
fixed the issue. It now pulls the most recent data for the user.

Was this reply helpful? Yes No