CDS updated data not reflecting after it's updated by the user, using Liquid code or Directly in Entity list

(0) Share

Report

Posted on by Community Power Pla...

Hi Experts,

I am facing one weird issue related to data fetch via liquid code or displaying data in entity list.

The scenario is like below:

1. When Users insert a new record to the entity then it is coming fine in Entity List and while fetching from Liquid code.

2. But when the same record is updated by the users, let's say publishing state from Draft to Published. then it is not reflecting that updated value in entity list or even while fetching from liquid code.

3. When I edit the Portal App, and click on the sync Configuration then after login again it starts showing the updated value both in Entity List and via Liquid code.

Why this is happening? is this the way it behaves? Any fix I can apply to resolve this issue?

Please help me with this issue.

Thanks,

Amit

Categories:

Power Apps portals

I have the same question (0)

All responses (3)

Answers (1)

oliver.rodrigues 9,368 Most Valuable Professional on at

Like (1)

Report

Hi

What you are facing is common and that's basically a caching issue.
You don't see the issue in your scenario 1 because it all runs in the same transaction, the Portal updates CDS data and invalidates the cache at the same time.
When updating data first in CDS, it might take up to 15 min for the cache to be cleared. Please refer to this post for more caching tips: http://oliverrodrigues365.com/2020/07/27/power-apps-portals-caching-tips/

For fetch/liquid you can add the timestamp condition and that should solve partially your problem

------------
If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Was this reply helpful? Yes No
Verified answer

justinburch Microsoft Employee on at

Like (1)

Report
Hi @Anonymous,
It sounds like you're facing a cache issue. In order to maintain performance, the Portal will cache all queries to Dynamics - this means that any data updated outside of the Portal (in CRM/CDS, via power automate, etc.) may not reflect. You can see some odd behavior by changing the sort order of your list (only works the first time, as each sort is a query - so it'll cache subsequent queries).
E.g.:
Entity List shows 4 records
User updates record 1, which triggers Power Automate to create a new record (record 5)
Entity List still shows 4 records
User clicks Name to change from ASC to DESC sort order
Entity List now shows 5 records
User clicks Name again to change back to ASC sort order
Entity List now shows 4 records again
There are a few tips you can utilize to try to force this cache to be less frustrating:
Make sure all entities utilized have Change Tracking enabled
Try to handle all non-Portal updates with synchronous code
Try to update from Portal - e.g. if possible, use "On Submit" Entity Form Metadata to set fields the user isn't setting
If retrieving from code, make the call unique by adding something random - e.g. if you're doing a Web API retrieve, in your fetchxml tag, add a condition like:

<condition attribute="new_name" operator="ne" "{{ params.dt }}">

Where dt was passed as a simple "new Date()"
I hope this helps,
Justin

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @justinburch @OliverRodrigues

Thanks for your response.
It helps me to resolve the issue.

Thanks,
Amit

Was this reply helpful? Yes No