Share
Report
5First of all, I hope this is the right forum.
Is there a way to selectively invalidate cache for certain entities in Powerapps portals? If not, is there a plan to do this in future? I have already turned on change tracking on the entity, but the portal either does not update at all, or definitely does not update fast enough.
To give you a use-case, imagine you have a application and approvals process, where the approval can happen both in Dynamics and on the Portal, but all applications are made through the Portal, and there's a bunch of workflows/flows that kick in as part of the process. The problem would be that all changes made outside of the portal, including changes to data by workflows/flows and even the Dynamics approvals are not reflected on the portal in a timely manner. If there was a way to invalidate cache for the application status entity for instance, so that whenever it is loaded, you get the most up-to-date status.
Another example is say there is a requirement to have a list of last viewed applications on the approver's home screen. This means that every time an application is viewed, this fact needs to be logged in a separate entity. At the moment, this is done using Power Automate (http trigger), so the entity creation is technically done outside the portal (Please feel free to suggest better ways of achieving this). The problem is that this list is again not reflected on the portal in a timely manner.
If there are better ways of achieving both, I am open to suggestions or just an answer to the original question would be fine.
All responses (
Answers (
