Server-side cache in portals

Note

Effective October 12, 2022, Power Apps portals is Power Pages. More information: Microsoft Power Pages is now generally available (blog)
We will soon migrate and merge the Power Apps portals documentation with Power Pages documentation.

As a portal administrator, you can clear the server-side cache for the entire portal so that updated data from Microsoft Dataverse is immediately reflected on the portal. Updates from Dataverse are communicated to the portal in asynchronous mode, so there might be a lag between the time data is updated in Dataverse and the time that updated data appears on the portal. To eliminate this delay—for example, when it interferes with portal configuration—you can force the portal to refresh its cache immediately.

Important

Steps to clear portal server-side cache

To clear the server-side cache:

  1. Sign in to the portal as an administrator.

  2. Navigate to the URL as follows: <portal_path>/_services/about.

  3. Select Clear Cache.

The server-side cache is deleted, and data is reloaded from Dataverse.

Clear the portal cache.

Configuration table caching in portals with capacity-based licenses

Capacity based portals have more options on <portal_path>/_services/about:

Clear portal cache with capacity-based license.

To learn more about the differences between Power Apps portals and portal add-ons, read Power Apps portals, Dynamics 365 portals and add-on portals.

Portal metadata is stored in tables called configuration tables. If you change configuration tables using the Unified Interface application, you must select Clear config to clear the configuration cache for changes to reflect in your Portal.

List of configuration tables refreshed when you clear config

Clearing the server-side configuration cache for a portal includes refreshing the data from the following configuration tables:

adx_contentaccesslevel

adx_contentsnippet

adx_entityform

adx_entityformmetadata

adx_entitylist

adx_entitypermission

adx_entitypermission_webrole

adx_externalidentity

adx_pagealert

adx_pagenotification

adx_pagetag

adx_pagetag_webpage

adx_pagetemplate

adx_portallanguage

adx_publishingstate

adx_publishingstatetransitionrule

adx_publishingstatetransitionrule_webrole

adx_redirect

adx_setting

adx_shortcut

adx_sitemarker

adx_sitesetting

adx_urlhistory

adx_webfile

adx_webfilelog

adx_webform

adx_webformmetadata

adx_webformsession

adx_webformstep

adx_weblink

adx_weblinkset

adx_webnotificationentity

adx_webnotificationurl

adx_webpage

adx_webpage_tag

adx_webpageaccesscontrolrule

adx_webpageaccesscontrolrule_webrole

adx_webpagehistory

adx_webpagelog

adx_webrole_systemuser

adx_website

adx_website_list

adx_website_sponsor

adx_websiteaccess

adx_websiteaccess_webrole

adx_websitebinding

adx_websitelanguage

adx_webtemplate

Caching changes for portals with version 9.2.6.x or later

Power Apps portals with version 9.2.6.x or later benefit from improved caching functionality to increase consistency and reliability as follows.

Important

  • No change to SLA for cache refresh (data transfer between Dataverse and portal) mentioned earlier in this article.
  • Data changes done using portals will reflect immediately in Dataverse and portals.
  • No change to clear server-side cache functionality. You can continue to use this functionality to clear server cache immediately.

FAQs

1. Can I change the cache refresh duration from 15 minutes to a lesser duration?
No. SLA for cache refresh remains 15 minutes. Any changes from Dataverse will reflect on portals within 15 minutes.

2. I'm using plugins or workflows to update data in other tables and need these data changes to reflect immediately on my portal.
This design approach isn't recommended. Except the primary record where the create or update action is triggered, data reflection from Dataverse to portals is never guaranteed to be immediate.

3. Is there any difference in caching between capacity-based portals and add-on portals?
No.

4. How long does it take for changes to reflect from portals to Dataverse?
Immediately, as long as the update changes a primary record and isn't based on indirect changes to data using plugins or workflows.

Next steps

Understand how portals connects to Microsoft Dataverse environment

See also

Build a portal using portals Studio