Unmanaged layers in Production environment

(0) Share

Report

Posted on by inanoffice23

299 Moderator

I asked Copilot how did an unmanaged layer occur, and it seemed to suggest that unmanaged layers are created if we go directly to the app or flow from the left menu, rather than entering first the solution, then the app or flow

It sounds like a 'branch' is created because the user didn't start the journey from the solution. Do you think this is accurate? I guess it makes sense

Issue: I have an app that only exists in Production (don't ask I didn't build it!) and has an unmanaged layer, trying to sort it but the 'remove layer' doesn't get enabled at all. I suspect I might have to export into Dev and push into Prod, hope that works to fix it but any ideas would be welcome too. Trying to use Xrmtoolbox but unsure how to specify the environment the culprit is

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

MS.Ragavendar 6,334 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@inanoffice23,

Is you solution (Power Apps) using any flow for powerapps, did u tried refreshing the flows from the app or did u publish the app anytime after the app is moved to production.

These are few cases, where the unmanged layer gets created in the managed solution.

Was this reply helpful? Yes No
Suggested answer

Gabriel G. 831 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi there,

Unmanageds layer happen when you edit a component directly in a managed environment. If you have an unmanaged layer on a component, you will see something like that:

You can select the row and then the 'remove layer' will become available.

Segundo, you should never create a new flow/component directly in a managed environment. For sure, you will create issues!

Otherwise, your issue is not an unmanaged layer. Since it is only 1 component, I suggest you to duplicate your flow in an unmanaged environment and then redeploy it in your production environment to make sure you have the component in developer environment.

____________________________________________

Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.

Was this reply helpful? Yes No
inanoffice23 299 Moderator on at

Like (0)

Report
Copy link

Link copied!

The app was only built in Production by someone else, just trying to fix the problem

The 'remove layer' doesn't work at all because it is not a managed solution

Xrmtoolbox advised there are many flows (over 40) with an unmanaged layer, so I suspect I'll have to re-import a new solution from Dev to Prod and get rid of the old one, thank you however for your responses

Was this reply helpful? Yes No
Ram Prakash Duraisamy 5,714 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @inanoffice23

Try below steps to delete the same.

1. Navigate to https://make.powerapps.com

2. Click On Solutions

3. Search for Default Solutions

4. Search for the Tables

5. Search for Columns

6. Select the Columns and Select the Unmanaged Layer component and delete the same.

Please mark as answer if my suggestion helps.
Subscribe here for More Useful videos : https://www.youtube.com/@rampprakash3991

Was this reply helpful? Yes No
Suggested answer

Fubar 8,487 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

If a new Solution was created in your Prod (or the Default Solution was used), new items that were created will be in the unmanaged layer, updates to other items that were in the environment from a Managed Solution will have an unmanaged layer sitting above the manged layers. Similarly you can get unmanaged layers if an unmanaged Solution was imported. The main issue will be where there are items that were updated and there is an Unmanaged Layer sitting above the Managed Layers.

Note: you will probably want to move the changes using an Unmanaged Solution down to your Dev environment prior to removing the layers otherwise you could lose the changes that were made (assuming the changes should be kept).

Was this reply helpful? Yes No