I have a Microsoft Dynamics CRM client that was adding some fields to both their Lead and Opportunity entities and was getting frustrated when the values they put into the Lead fields would not show up in the corresponding Opportunities created from the Leads.
One of the “quiet” features of Dynamics CRM that sometimes causes confusion is the Field Mapping in relationships.
The purpose of field mappings is to copy certain values (e.g. address fields) from a record to an associated record (e.g. an Opportunity created from a Lead, a Contact created from an Account).
Please note that this is just a copy mechanism when the record is created. Updating values in the target entity will not roll back up to the source entity, and updating values in the original record will not roll down to the child entity. For example, updating an address in accounts will not update the address in contacts.
There are other ways to achieve those requirements (quick view forms, workflows, plug-ins, etc).
The following are simple steps to create relationship field mappings.
In Customizations, find the Lead Entity, and then find the “1:N Relationships”.
Locate the relationship to which you want to carry values over (in this case, lead to opportunity).
In the relationship editor window, click on Mappings.
Locate the SOURCE from the starting entity (Lead) and the TARGET, which is the destination entity (Opportunity) and select the fields to be mapped. NOTE: This must match “type” (e.g. Text to text)
Choose OK to save, and then publish. The mapping is now established.
Things to Note:
- Field types must match.
- Data will only be copied from source to target when you create the one record from the other, in this case when you convert the Lead record. If you update this field in the Opportunity record, it WILL NOT update the Lead record. In this case the Lead record will be set to closed, but if reopened, updating that field in the Lead WILL NOT update the Opportunity. There are other methods (Quick View Forms, Workflows, etc) that can do this.