Publishing App version

(0) Share

Report

Posted on by jaina

517

Dear Experts,

Good day!

Could you kindly help identify the cause of the delay some users experience in seeing the additional field after publishing changes? While some users may take up to a day to view the changes, others do not see them at all. What measures can be taken to ensure the changes are reflected immediately after publishing?

I appreciate your insights. Thank you very much!

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

SwatiSTW 741 Super User 2025 Season 2 on at

Like (1)

Report

Though we can ask users to clear their browser cache and cookies is an option, which is not always feasible, Therefore i will suggest following two solutions-

A. Use a central data source to store app version:

1. Create a data source (e.g., SharePoint or Dataverse) with a record like:
{SettingName: "AppVersion", SettingValue: "1.0.1"}
2. On App Start, fetch the latest app version:
   Set(CurrentVersion, "1.0.1"); // Local app version
   Set(ServerVersion, LookUp(AppSettings, SettingName = "AppVersion").SettingValue);
3. Compare versions and reload if needed:
   If(ServerVersion <> CurrentVersion,
       Notify("A new version of the app is available. Reloading...", NotificationType.Information);
       Exit(true);
   );
4. Publish the updated app and increment the SettingValue in the data source.

B. Use local storage for version control:

1. Load the locally stored version on app load:
   LoadData(LocalAppVersion, "LocalVersion", true);
   If(IsBlank(LocalAppVersion),
       Set(LocalAppVersion, "1.0.1"); // Default to the current version
   );
2. Compare the local version with the server version and update:
   If(ServerVersion <> LocalAppVersion,
       Notify("A new version is available. Reloading...", NotificationType.Information);
       SaveData(ServerVersion, "LocalVersion");
       Exit(true);
   );
3. Refresh the app to ensure users always get the latest version.

Was this reply helpful? Yes No
jaina 517 on at

Like (0)

Report

Hi @SwatiSTW, thanks for your recommendation. However, i just wan to clarify if this can also be achieved in a custom form in SharePoint List using Power Apps?

Was this reply helpful? Yes No
Suggested answer

SwatiSTW 741 Super User 2025 Season 2 on at

Like (0)

Report

@jaina Yes, the approach can also be implemented in a custom form for a SharePoint List using Power Apps, Follow below steps

1. Store the version of your form in a SharePoint list.

Create a list named VersionControl with two columns: Title (text) and VersionValue (text).
Add a record:
Title: FormVersion
VersionValue: 1.0.1

2. When the form loads, check the current version from the list. In the OnStart property of the form, add this code:

   Set(CurrentVersion, "1.0.1"); // The version currently running in the form
   Set(ServerVersion, LookUp(VersionControl, Title = "FormVersion").VersionValue);

3. Compare the version from the list with the version in the form. In the OnVisible property of the form screen, add this

   If(ServerVersion <> CurrentVersion,
       Notify("A new version of the form is available. Reloading...", NotificationType.Information);
       Exit(true); // Reloads the form to get the latest version
   );

4. Publish changes when updating the form - Update the VersionValue in the VersionControl list to the new version (e.g., 1.0.2) after making changes. The form will automatically detect the new version and refresh for all users.

Was this reply helpful? Yes No