Power Platform Community Forum Thread Details

Hi all!

I'm deploying a solution from the development environment to the production environment as a managed solution.

When I import the solution into the production environment and need to restore the app in order to publish the latest version, I do not find all versions and cannot publish the updated one.

Why? Can anyone help me?

Thanks

Categories:

Power Apps Pro Dev & ISV

Possible Causes & Solutions:

1. Solution Versioning in Managed Solutions

When you import a managed solution, the versioning works differently than in an unmanaged development environment.
Power Apps does not keep all historical versions of an app in a managed solution.
Only the latest deployed version should be available.

✅ Solution:

Ensure that you are importing the correct solution version.
In Power Platform Admin Center, check Solutions > Managed Solutions and verify the Version Number.

2. Component Behavior in Managed Solutions

Some components, like Canvas Apps and Model-Driven Apps, behave differently when deployed as managed.
When a managed solution is imported, the latest published version from Development is the one that appears in Production.
However, draft versions that existed in Dev will not be available in Prod.

✅ Solution:

Make sure you publish the app in the Development environment before exporting the solution.
If necessary, increment the version number before export (e.g., 1.0.0.1 → 1.0.0.2).

3. Publishing Issue After Importing

Sometimes, after importing a managed solution, Power Apps does not immediately recognize the latest version.
This can happen due to caching or syncing delays.

✅ Solution:

Try refreshing the app list by navigating to:
Power Apps > Apps > Click "Refresh".
Clear browser cache and try again.
Wait a few minutes and check again.

4. Conflicts with Earlier Imported Versions

If an older version of the managed solution already exists in Production, the imported version might not replace it correctly.
Power Apps should replace the older version if it's a higher version number, but sometimes dependencies prevent this.

✅ Solution:

Manually remove the existing managed solution and import the new version again.
Be cautious: Removing a managed solution deletes all components added by it.

5. App Not Set as Default for Publishing

If multiple versions of the app exist, the new version may not be set as the default.

✅ Solution:

Open the Power Apps list, locate your app, and check if the latest version is marked as "Current Version".
If not, restore the latest version.