Alex
Alex

Reputation: 23300

Error stating Entity map does not exist on target when the solution contains no relationships

I start in the DEV environment

I exported the solution as Unmanaged

I opened the STAGING environment (same as DEV except for the customizations I'm trying to bring over from DEV)

I tried to import the solution. Import fails.

This is the error (copy-pasted from the log file, reformatted for readability):

Entity Mapping

businessunit-opportunity

Failure

0x80048010

EntityMap businessunit -> opportunity - Import: FAILURE. This entity map does not exist on the target system.

What is the CRM trying (and failing) to do ? Everything related to Business Unit (custom and/or standard) already exists in the target environment, I literally only have this custom field to bring over (I can go and create it by hand of course, but I'd rather stick to solutions...)

Upvotes: 2

Views: 3911

Answers (2)

Henrik H
Henrik H

Reputation: 5787

This issue can be caused by having a reference in your solution to a relationship (e.g. a subgrid using a custom relationship) that is not included in the solution. CRM will not complain when exporting the solution, but will fail on import with the above error.

Resolve the issue by adding the relationship (and necessary lookup field in the case of 1:N/N:1-relationships) to the solution.

Upvotes: 1

Daryl
Daryl

Reputation: 18895

Check the customization file for a mapping from between BusinessUnit and Opportunity, with no actual mappings define. Delete the XML for that mapping and try to import again.

Upvotes: 1

Related Questions