How to remove Unmanaged customizations on Managed component

This is a common issue everyone would have faced once in a while that the customizations were not getting applied on the target instance through solution deployment. This is due to the direct changes on the component which is part of managed solution.

A component which is managed, gets an unmanaged layer as soon as you edit it directly on the instance. This unmanaged (active) layer lays on top of all other layers, which are coming from the different solutions containing this component. The layer on top is always winning, hence you can’t see the new changes coming from new deployments.

To avoid this issue, Microsoft introduced a new feature called “Solution Layers” where you can see all solutions where this component is part of it. You can see one “Active” solution on top of all solutions if you would have changed something directly on the instance. So, to get rid of the unmanaged customizations on managed component, you have to follow the below steps.

  1. Select the component and Click on “Solution Layers” button (some times you can see this option under “More Actions” drop down menu).

2. On click of this button, it will show the list of all solutions which included selected component, as shown in the below screenshot.

3. Select the 3 dots (…) of “Active” solution row, select “Remove Active Custmoziations” option and confirm.

4. That’s all you have to do to remove all unmanaged customizations, after that the changes will be affected which are coming from new deployments.

I faced this situation so many times, the changes I have done for ex. in web resources in dev instance couldn’t transfer to UAT/Prod instance due to the “Active” solution layer. So with this new feature, you could remove this unwanted solution layer with a single button click.

Note: Microsoft not yet rolled out this feature for some components like Views and Fields. (Thanks Viswanath for highlighting this in your comment)

Hope it is helpful….


4 thoughts on “How to remove Unmanaged customizations on Managed component

  1. Hello Phani
    wanted to add one more note : this removing of layers feature, Microsoft has rolled-out only for Forms but not yet views and fields.

  2. Thanks for this post! I follow the steps and until 4 no problems. However, I do get an error message: “Unable to remove active customizations. RemoveActiveCustomizations is not supported for components of type Entity.” I particularly want to remove a Metadata setting, do you happen to know if that falls under the same category as “Views and fields” ie not rolled out yet? (And if so, would you happen to know any timelines?

  3. Hi Phani,
    thanks for posting!
    I wanted to delete an unmanaged layer from an App but I am not sure the datas which have been collected with this unmanaged app will be lost or nor.
    I have built several forms in my app and their target table are also in my solution. Also in my solution I have an app and 4 tables.
    If I remove the unmanaged layer from the App, will this removement affected my tables? Do you have an idea?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s