Microsoft Dynamics 365 | Integration, Dataverse...

Error Importing Managed Solution – ImportAsHolding failed (EntityMap component)

(2) Share

Report

Posted on by Saidev3

Hello everyone,

I am currently attempting to move a master solution from our DEV environment to QA as a managed solution, but I am encountering the following error:

"Solution {SolutionName} failed to import: ImportAsHolding failed with exception: The uninstall operation will delete the base layer for the component 'EntityMap' with id {GUID}. The operation cannot continue because there are other managed layers over the base layer. You can use the solution layers to find out which other solutions are blocking the operation."

Has anyone experienced this issue before and found a resolution? I would greatly appreciate any guidance or suggestions on how to resolve this.

Update 1 : I identified that guid mentioned in the error message is related to the 'opportunity_originating_lead' out-of-the-box relationship mapping, where we have added mappings for a few custom fields. I tried moving an unmanaged solution containing this relationship from DEV to QA to see if that would resolve the issue, but the error persists.

Thank you in advance for your help!

Categories:

Dynamics 365 general

I have the same question (0)

All responses (6)

Answers (0)

Anupam.khasia 170 on at

Like (0)

Report

Hello @Saidev3,

This is because you have directly made changes into components of your solution in QA environment.Whenever you directly modify components under "Default Solution" for components used in managed solutions , it will generate solution layer. You have to remove this solution layers before importing your solution.

https://learn.microsoft.com/en-us/power-platform/alm/solution-layers-alm

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/solution-layers

You can remove solution layers from ... options for each component.

Please mark this as resolved if it helps you.

Thanks

Anupam

Was this reply helpful? Yes No
Saidev3 28 on at

Like (0)

Report

Hi @Anupam.khasia,

Thank you for the response.

I identified that GUID mentioned in the error message is related to the 'opportunity_originating_lead' out-of-the-box relationship mapping, where we have added mappings for a few custom fields. To fix the issue, I moved an unmanaged solution containing this relationship from DEV to QA to see if that would resolve the issue, the unmanaged solution got moved but when trying to move Master solution as managed the error persists and now when I am checking for solution layer on the relationship component, It is showing only 1 managed layer.

Was this reply helpful? Yes No
Suggested answer

Anupam.khasia 170 on at

Like (1)

Report

Hello @Saidev3,

Fix you applied should not work as per my knowledge. What you need to do is

* Remove unmanaged layers from entire solution from QA.

* Add changes which you directly made into QA in Dev environment

* Add changes into your solution

* Export your solution as managed

* Import as Managed

You have to remove any unmanaged layers in your solution of QA environment.

Thanks

Was this reply helpful? Yes No
CU25071753-1 13 on at

Like (1)

Report

Has anyone identified a solution for this?

I am facing the same issue while importing a solution containing opportunity_originating_lead. The suggested solution doesn't work as there is no unmanaged layers to remove. There is only a single entry under the solution layers and that is msdynce_Sales.

Was this reply helpful? Yes No
Suggested answer

CU25071753-1 13 on at

Like (0)

Report

For anyone facing the same issue while importing a solution with the opportunity_originating_lead relationship but no unmanaged changes in the target environment, here’s what I found:

There is an AttributeMap table in D365 that stores individual field mappings, where each record represents a field mapping within a relationship. All of these AttributeMaps are linked together under the EntityMap which is associated with the relationship.

In my case, there was another Managed Solution that I imported a while back in the QA which had ownership of these AttributeMap records. Since there is no direct way to view solution layers for the AttributeMap in D365, I used FetchXML Builder in XRMToolbox to display all the AttributeMaps associated with the EntityMap that was throwing the error. The solution field in the result showed that the ownership belonged to the older Managed Solution.

In the main solution upgrade I was importing, I had added the opportunity_originating_lead relationship and had removed some of the field mappings(AttributeMaps) from it in DEV. However, in QA, the AttributeMaps I had deleted were owned by the older Managed Solution, which prevented their deletion during the import of my Main Solution and triggered the EntityMap error.

I resolved the issue by adding all the components from the older Managed Solution into my Main Solution in DEV and then deleted the older managed solution in QA. After doing this, I was able to import the Main Solution without any issues.

Alternatively, If you don't want to delete the older Managed Solution in QA and you're okay with keeping the field mappings, a temporary workaround would be to add back any field mappings you may have deleted. This will also allow the import to proceed successfully, but it’s not a permanent fix.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,397 on at

Like (0)

Report
Hello,

Thank you for providing the detailed context.

The error message:

“ImportAsHolding failed with exception: The uninstall operation will delete the base layer for the component ‘EntityMap’... because there are other managed layers over the base layer.”

typically occurs when a managed solution attempts to overwrite or remove a component (in this case, an EntityMap) that is already part of another managed solution in the target environment. This is a common issue when dealing with solution layering in Dynamics 365.

Recommended Resolution Steps:

Use Solution Layers Tool
In the Power Platform Admin Center or Advanced Settings, navigate to the Solution Layers view for the affected component (e.g., opportunity_originating_lead relationship). This will show you:

Which solutions are contributing layers to the component.

Whether the base layer is part of a managed solution that cannot be removed.

Remove Dependent Managed Layers
If possible, uninstall the managed solutions that are layering over the base component before importing your new managed solution. Be cautious, as this may affect other dependencies.

Convert to Unmanaged for Migration
As a workaround, consider importing the solution as unmanaged into QA, especially if this is a non-production environment. This avoids the layering conflict and allows you to validate the changes.

Split the Solution
If the issue is isolated to a specific relationship or mapping, create a separate solution containing only that component and import it first. This can help isolate and resolve the conflict before importing the full solution.

Avoid Customizing OOTB Relationships in Managed Layers
If possible, avoid adding custom mappings to out-of-the-box relationships in managed solutions. Instead, consider using custom relationships or handling mappings via code or workflows.

If this response helps resolve your issue, please consider marking it as accepted so it may assist others facing similar challenges.

Best regards.

Was this reply helpful? Yes No