Update made on the portal via an Entity Form If you do the reverse, that is update data from the portal to Dataverse (via an Entity Form or Web Form) then the data is updated immediately in Dataverse and immediately visible in an app. This will usually take only a few minutes but might be as long as 15 minutes (based on the SLA). If I go to the portal, there is no immediate visible change, as the cache has not yet refreshed. So if I view a record on the portal Record on PortalĪnd then update the record in a model-driven Power App and save Update record in Dataverse The actual SLA (service level agreement) is 15 minutes, as per Microsoft documentation. The downside is that if you have updates made to Dataverse, either using an internal app (such as Dynamics 365 or a custom model-driven app) or updates via flow or other integrations, you may not see this updated data on the portal for quite a few minutes. If it did, the performance of the portal would be incredibly slow. This means that the portal does not make a direct request back to the Dataverse for each individual data update. That works fine for development and administration, but what about day to day usage of the portal? The Power Apps portal uses caching to increase overall portal performance. Clearing the Cache How Power Apps portal Caching Behaves The process is so popular that even world famous podcasts use it as a title. You are likely very much aware of the Portal studio Browse Website function or the Clear Cache button available in the /_services/about page for administrators.Ĭlearing the cache ensures that all the latest updates to the portal metadata as well as Dataverse info are visible on the Power Apps portal. If you work with building Power Apps portals, as you make updates to pages, assign users to Web Roles or make any other changes, you want to see these changes immediately on the portal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |