Showing results for 
Search instead for 
Did you mean: 

New function: RefreshApplication() to force entire app to reload


Every time I make a change to the Power App applications for my organization (not changes to the datasources, but the actual app) my users do not receive the updates, even if they close and re-open the application. Instead they have to slide the 3 buttons on the left side of the screen and hit the powerapps refresh button and then relaunch the application. Most users arent aware of the 3 buttons on the left, and this "workflow" is not very intuitative. Forcing the users to uninstall and reinstall is even worse of a work around.


Is there any way to force the app to do a full-refresh like there is for refreshing datasources (ie refresh(datasource) ).... maybe something like "RefreshApplication()"?



Related to these posts:

Status: Under Review

We are investigating options. Thank you for your feedback and patience,



Not applicable


Frequent Visitor


Advocate I

yes please.....very much needed here!

Advocate I

Is this still under review since 2018?

Frequent Visitor

+1 - this is needed and could be useful.  Right now I get around it by writing the version number to a SP list.   The app does a lookup for the version number.  If it changes, I force a warning message that the app has been updated and needs to be reloaded.   This is irritating to some users and would be better if I could just change a trigger and everyone's app would just reload automatically.

Advocate V
Advocate V

Is there a better way to reload an App in the player other that hitting the Browser Refresh button at least THREE times?

Frequent Visitor

Most web browsers pull from a cache on your computer.  To get around it, hold down the CTRL key and press the browser refresh button.  This forces the browser to pull all new information from the web and not your computer.

Advocate II

Still under review from 2018? No updates?



Frequent Visitor

Another option I've used is write a version number to a database / list somewhere.  Then have the app do a comparison to the internal version # written within the app to this database list.  You can have the app check the database at various times or when you change screens, or after certain data is saved, etc... 


If the database has a newer / higher / different number, then a large warning box comes up on the app that blocks all usage of the app until the user does a refresh.  In a sense, the app becomes useless if the version # doesn't match.  Once they download and refresh the app, the warning goes away because the version #'s match again.


Just an idea for those trying to be creative to get around this....