Unanswered

Saving changes in Portal Studio and Portal Management - the cache

(0) Share

Report

Posted on by Christopher Grace

When developing Portals, and troubleshooting, it is common to try different settings, save the changes, and browse the portal to see the effect.

Sometimes the changes take effect immediately. Sometimes there is a delay. In my experience, this is one of the single most time-consuming issues impacting Power Apps Portals adoption.

Microsoft improved caching in mid-2020. MS Docs says

Capacity-based portals and add-on portals will use the same caching functionality.
Capacity-based portals don't have to manually clear the configuration table cache.

The first statement is ambiguous, possibly contradicting the second. Has anyone else experienced delays in config changes taking effect? How do you manage it?

Categories:

Power Apps portals

I have the same question (0)

All responses (2)

Answers (0)

oliver.rodrigues 9,368 Most Valuable Professional on at

Like (0)

Report
Yeah I find those statements confusing as well.

Capacity-based portals and add-on portals will use the same caching functionality.

This one I think is fine, is basically to say Power Apps Portals and Dynamics 365 Portals Add-On works the same way

Capacity-based portals don't have to manually clear the configuration table cache.

The 15 min SLA will clear the Portal cache, including transactional data and configuration data, so you "don't need" to clear the cache manually

During DEV, you must clear cache manually as it's just not practical to wait the 15 mins SLA

Please take a look at this article to see a few tips: http://oliverrodrigues365.com/2020/07/27/power-apps-portals-caching-tips/

The JavaScript I have there is a life changer

In general a few easy ways to clear cache:

JavaScript bookmark from my article (need to be signed-in as admin)

Open Portals Studio and click Sync Configuration

Open Portals Studio and click Browse Website

Was this reply helpful? Yes No
Christopher Grace 35 on at

Like (0)

Report

I submitted a request to the documentation team for clarification. If it is still subject to the 15 minute SLA, that seems no different from the previous version.

Was this reply helpful? Yes No