cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Helper I
Helper I

Portal caching issue

I am creating a record in one of my entities (entity1) through my portal using the OOB 'Create New Record' function.

On creating a new record through the portal, a Power Automate runs and creates a set of related records in another table (entity2) for the new record.

When I try to view these records from entity2 in the portal (through a subgrid added on my detail form), they are not visible immediately. Clearing server side cache works, but that is a manual process.

 

How can i ensure that the newly created records are visible in the portal subgrid?

1 ACCEPTED SOLUTION

Accepted Solutions
Microsoft
Microsoft

Hello @TheIntern ,

 

If you are associating items by making direct calls to CDS(via flow in this case), then it is not expected that grid will refresh automatically. It will be bound by the cache invalidation sla which is 15 mins.

One way to force refresh of subgrid it is by making a change to that (entity2)entity from portal itself.

 

 

Cheers!

Pranjali

View solution in original post

4 REPLIES 4
Frequent Visitor

Hi @TheIntern 

 

The default SLA, CDS record updates will reflect in power Apps Portal in 15 minutes.

Can you enable the 'Change Tracking' feature for both entity1 and entity2 to check the related records are displayed on portal.

 

--------------------------------------------------------

If you find this post helpful consider marking it as a solution to help others find it.

Thanks,

Satya

Thank you for the response @satyarkar 

 

I checked the entities, and the 'Change tracking' feature is enabled for both.

Super User II
Super User II

Hi @TheIntern , actually the Change Tracking option won't make a difference anymore.

Like mentioned by @satyarkar, as your process is running in the background, this will take up to 15 min for the Portal to refresh your data.

 

In regards with your Power Automate flow, does it have to be a power automate flow? are you doing any complex integration that it requires power automate? if not, I would consider using Plugins/Workflow in your Dataverse (CDS), and they would have to be a sync/real-time process.

Whenever we have a sync process starting via Portals, the cache is automatically invalidated.

 

Take a look at this article for more tips: https://oliverrodrigues365.com/2020/07/27/power-apps-portals-caching-tips/

 

more info on workflows: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/workflow-proce...

more info on plugins: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/plugin-develop...

 




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.

Power Apps Portals Super User


Oliver Rodrigues


 

Microsoft
Microsoft

Hello @TheIntern ,

 

If you are associating items by making direct calls to CDS(via flow in this case), then it is not expected that grid will refresh automatically. It will be bound by the cache invalidation sla which is 15 mins.

One way to force refresh of subgrid it is by making a change to that (entity2)entity from portal itself.

 

 

Cheers!

Pranjali

View solution in original post

Helpful resources

Announcements
secondImage

Experience what’s next for Power Apps

Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

New Power Super Users

Congratulations!

We are excited to announce the Power Apps Super Users!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

Users online (55,230)