You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/maker/portals/admin/clear-server-side-cache.md
+5-9Lines changed: 5 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: neerajnandwana-msft
5
5
ms.service: powerapps
6
6
ms.topic: conceptual
7
7
ms.custom:
8
-
ms.date: 07/20/2020
8
+
ms.date: 07/21/2020
9
9
ms.author: nenandw
10
10
ms.reviewer: tapanm
11
11
---
@@ -14,15 +14,15 @@ ms.reviewer: tapanm
14
14
15
15
As a portal administrator, you can clear the server-side cache for the entire portal so that updated data from Common Data Service is immediately reflected on the portal. Updates from Common Data Service are communicated to the portal in asynchronous mode, so there might be a lag between the time data is updated in Common Data Service 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.
16
16
17
-
> [!NOTE]
17
+
> [!IMPORTANT]
18
+
> - Clearing the [portal server-side cache](#steps-to-clear-portal-server-side-cache) or the [configuration entities cache](#configuration-entity-caching-in-portals-with-capacity-based-licensesa-name--configuration-entity-caching-portals-with-capacity-based-licensesa) causes temporary performance degradation of the portal while data gets reloaded from Common Data Service.
19
+
> - Changes to the [configuration entities](#list-of-configuration-entities-refreshed-when-you-clear-config) should be performed during non-peak hours.
20
+
> - Frequent or too many configuration entity changes may adversely affect portal performance.
18
21
> - The SLA for cache refresh (data transfer between Common Data Service and portal) is 15 minutes.
19
22
> - Power Apps portals with version 9.2.6.x or later have improved caching. For more information, go to [Caching changes for portals with version 9.2.6.x or later](#caching-changes-for-portals-with-version-926x-or-later).
20
23
21
24
## Steps to clear portal server-side cache
22
25
23
-
> [!IMPORTANT]
24
-
> Clearing the portal server-side cache causes temporary performance degradation of the portal while data gets reloaded from Common Data Service.
25
-
26
26
To clear the server-side cache:
27
27
28
28
1. Sign in to the portal as an administrator.
@@ -45,10 +45,6 @@ To learn more about the differences between Power Apps portals and portal add-on
45
45
46
46
Portal metadata is stored in entities called *configuration entities*. If you change configuration entities using the *Unified Interface application*, you **must** select **Clear config** to clear the configuration cache for changes to reflect in your Portal.
47
47
48
-
> [!IMPORTANT]
49
-
> - Changes to the [configuration entities](#list-of-configuration-entities-refreshed-when-you-clear-config) should be performed during non-peak hours.
50
-
> - Frequent or too many configuration entity changes may adversely affect portal performance.
51
-
52
48
### List of configuration entities refreshed when you clear config
53
49
54
50
Clearing the server-side configuration cache for a portal includes refreshing the data from the following *configuration entities*:
0 commit comments