A managed solution cannot overwrite the AttributeMap component ....

(0) Share

Report

Posted on by l ringel

Hi there,

I am trying to import an update to my current solution and am receiving this error.

"A managed solution cannot overwrite the AttributeMap component with Id=f3aa3ba7-997b-e711-810c-e0071b6a10b1 which has an unmanaged base instance. The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged AttributeMap component on the target system, and now a managed solution from the same publisher is trying to install that same AttributeMap component as managed. This will cause an invalid layering of solutions on the target system and is not allowed."

The error log shows that lead-contact is causing this error. I have recently made a few mapping changes within our live site. so i went back and removed those changes to see if that would make the difference but it didn't.

can anyone help me with this.

Thank You!

Leibish Ringel

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

Hi,

Is this On-Prem or Online?

If On-Prem, you can check which mapping is causing this issue by going into SQL and executing the following command:

select SourceEntityName, SourceAttributeName, TargetEntityName, TargetAttributeName from AttributeMap am

left outer join entitymap em on em.entitymapid = am.EntityMapId

where am.AttributeMapId='f3aa3ba7-997b-e711-810c-e0071b6a10b1'

Once you get the component, remove it from the target system and try re-importing it.

Hope this helps.

Was this reply helpful? Yes No
l ringel on at

Like (0)

Report

Hi Aric,

Thank you for your respnse.

I am using Dynamics Online. Is there a way to do it with my version of Dynamics?

Was this reply helpful? Yes No
Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

Can you look at the 1-N and N-N relationships between lead and contact?

If you can find, either in log file or figure out which relationship is the one that is causing this issue (on production), remove it and try to reimport.

I did some searching and most solutions are for On-Prem, not Online.

Was this reply helpful? Yes No
MMK 745 on at

Like (0)

Report

Hi Leibish,

Just remove the the EntityMap tag from Customization xml

<EntityMap>

<EntitySource>lead</EntitySource>

<EntityTarget>contact</EntityTarget>

<AttributeMaps>

<AttributeMap>

…

</AttributeMap>

</AttributeMaps>

</EntityMap>

Was this reply helpful? Yes No
Saddamk206 777 on at

Like (1)

Report

Remove the EntityMap tag from Customization xml

Extract the solution .zip file, open customization.xml and search with <EntitySource>lead</EntitySource> and then choose your source and target are the same entity name.

Now replace the tag with <AttributeMaps /> and then create a solution's zip and import it again.

<EntityMap>

<EntitySource>lead</EntitySource>

<EntityTarget>contact</EntityTarget>

<AttributeMaps>

…

</AttributeMaps>

</EntityMap>

Was this reply helpful? Yes No
oliver.rodrigues 4,052 on at

Like (0)

Report

is there any other solution for this BESIDE removing the tag from the xml ?

Was this reply helpful? Yes No
Suggested answer

oliver.rodrigues 4,052 on at

Like (0)

Report

Hey guys.. just got this one solved

I was facing issue with both Contact-Lead and Incident-IncidentResolution in a clean Trial Environment

I navigated to the destination environment, opened the Relationship, opened the Mappings and DELETED the mapping that was causing the issue

Re-imported the solution and all went good

Was this reply helpful? Yes No
Suggested answer

moko33 1,788 on at

Like (0)

Report

We had this problem now when upgrading the Field Service solution from Version 7.5 to 8.7. MS Support provided us a nice step by step instruction for what to do:

support.microsoft.com/.../error-importing-attributemap-in-dynamics-365

Was this reply helpful? Yes No