web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Error on solution import : "incident-incident : Cannot overwrite the AttributeMap component"

(0) ShareShare
ReportReport
Posted on by

Hi,

While importing a managed solution, the following error occurs on the entity mapping 'incident-incident':

A managed solution cannot overwrite the AttributeMap component with Id=6c6480d1-5aa9-e511-80fc-3863bb348bb0 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.

I'm working on a CRM online 2015 organization but I've been able to reproduce it on a 30 days trial (CRM 2016).

The target environment does not contain any unmanaged solution.

I've been able to narrow the source of the problem : 

  1. At the first import of the solution, no problem.
  2. Then, on the target environment, I set the cascade closure preference in  "Parent and Child case settings" to "Don't allow parent case closure until all child cases are closed"
  3. If I try to update the solution , I get the error "Cannot overwrite the attributeMap..."

Note that I can perfectly update the solution before step 2 without any trouble.

According to msdn : When Parent and Child case settings are configured in the application, data is stored in  the organization entity

What I don't understand is why it prevents me from importing my solution, since this settings is not included in it (that's why I change the setting on the target environment directly).

My only workaround so far is to manually edit the customizations.xml in the zip solution file to remove  the content of the "AttributeMaps" node under the "EntityMap" node refering to the incident-incident mapping. Basically, I'm removing from the solution the mapping of attributes between a parent and child case. When I do that, I can import the solution without any trouble. 

Any Ideas ? 

 

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Bas van de Sande Profile Picture
    4,383 on at

    Hi Alexis,

    I think by changing the cascade closure preference in step 2, you actually implemented an unmanaged change. You implemented that change on top of the managed solution. When you do an update of the orginal solution on top of that, you get the situation that the managed solution wants to overwrite the unmanaged solution (your last change).

    One way of resolving could be (on a clean environment):

    1. import the managed solution

    2. create a new unmanaged solution and add the incident entity

    3. apply the cascading on the new solution

    4. publish the unmanaged solution

    5. update the orginal managed solution

    this way it should work

    Bas

  • Community Member Profile Picture
    on at

    Hi Bas,

    Thanks for your input, your explanation seems good regarding the error message

    I've tried what you suggested on a clean environment.

    The trouble is I can't "apply the cascading on the new solution", because, as far as I know, the only way of setting the closure preference for parent and child case is through Settings>Service Management>Parent and Child case settings (it is apparently not possible to set it directly from the incident entity)

    By doing this,  having an unmanaged solution containing the incident entity beforehand, I still get the error when trying to update my solution.

  • Andrew Monkey Profile Picture
    55 on at

    I am experiencing the same issue. Is there a solution that doesn't involve hacking the XML file each time the incident entity is added to a solution?

    The joys of Managed solutions :)

    Regards,

    Andrew

  • saadzag Profile Picture
    1,145 on at

    Can you export the solution without the relationship incident_incident?

    and import it as managed.

  • Suggested answer
    Kenny Vaes Profile Picture
    345 on at

    I was facing the same issue during one of our deployments of a managed solution. I ended up looking at the Relationship Mappings of both the Source and Target environments. I deleted all attribute maps (using the CRM user interface) from the Target Environment that were also present in the Source environment.

    After doing so, I could import the solution and in the underlying SQL tables, I could also see the attribute map records moving from IsManaged = 0 to IsManaged = 1

  • Suggested answer
    Loic Orue Profile Picture
    927 on at

    I experienced this issue today after modifying a 1:N relationship directly on the Target system.

    To fix it:

    - I performed a backup of the system.

    - I removed all of the Field Mappings (except the default one that can't be removed) from the relationship record.

    - I Imported the solution again. 

    Good luck!

  • Saddamk206 Profile Picture
    777 on at

    Remove the the EntityMap tag from Customization xml

    <EntityMap>

    <EntitySource>lead</EntitySource>

    <EntityTarget>contact</EntityTarget>

    <AttributeMaps>

    <AttributeMap>

    …

    </AttributeMap>

    </AttributeMaps>

    </EntityMap>

  • Suggested answer
    oliver.rodrigues Profile Picture
    4,052 on at

    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

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans