Power Platform Community Forum Thread Details

Which unmanaged customizations prevent applying a change in a new version of managed solution

Hello community,
is there any easy way to find which unmanaged customization does not allow a change in a new version of managed solution to be applied?

Here some details:
We have a dev environment with an unmanaged solution with core functionality - "CoreSolution".
Another staging environment where the "CoreSolution" is imported as managed solution and an unmanaged solution with customizations - "CustomerSolution".

We have made some changes in a custom entity into the "CoreSolution":
- added new column
- existing auto number column is changed from required to optional.

In "CustomerSolution" we have some customizations over this custom entity like:
- changes in status code values and their transitions
- new columns including relations to other tables
- changes in views and forms
- new views and forms

When we import the changed version of the "CoreSolution" as managed in the staging environment the new column is added, but auto number column remains required.
The import is made by Microsoft Power Platform Build Tools for Azure DevOps.

If we use "Overwrite unmanaged customizations" option all changes are applied.

We want to keep the customizations in the "CustomerSolution" and to apply all new changes as well, not only some of them.

Could not find any documentation to explain what kind of customization prevents applying some changes.

Thanks in advance

Categories:

Environment

Quick Links

Leaderboard > Power Apps - Power Apps Governance and Administering