Tip #1413: Components Required in the Solution for Relationship Mapping Deployment

Today’s winner is Linn Zaw “I always” Win. And you can be one too if you email your tip to jar@crmtipoftheday.com!

Have you ever added the 1:N or N:1 relationship into the solution, created new mappings in the solution and deployment the solution to another environment only to find out that the mappings are not deployed? Upon opening the customizations.xml of the solution, you might notice that the newly created mappings are not included under the <EntityMaps /> tag.

These are the components required in the solution to include the relationship mapping.

  1. Relationship which contains the mapping (obviously)
  2. Both Primary and Related tables of the relationship
  3. Target column of the mapping

Relationship

Screenshot of the classic interface for Relationship definition. Information tab is selected. The following screen elements are numbered: number 1 - Relationship name number 2 - Primary Entity name also number 2 - Related Entity name

Mapping

Screenshot of the classic interface for Relationship definition. Mappings tab is selected. The following screen elements are numbered: number 3 - row containing the mapping between source and target columns

Tables and target column

Screenshot of the classic interface for the solution components. Components > Entities node is expanded in the tree, Fields node under the target entity name is selected. The following screen elements are highlighted and numbered: number 2 - Primary Entity and Related entities under Entities node in the tree. number 3 - mapped target field selected in the list view in the right part of the screen.

Cover photo by Davies Designs Studio on Unsplash