foxhelp
asked on
Mapped fields in Microsoft Dynamics CRM 2013 On-line
I set up 8 custom fields in the lead record to move over to the contact record when the lead is qualified but 2 of the fields move over the wrong data. These two fields have data sets and it moves over the wrong one. There are other data set fields that do move over correctly. Can someone tell me what to check? There aren't that many options when it comes to mapping fields in CRM.
ASKER
I checked and there are no workflows/processes registered on Lead Status change.
Field mapping is a feature of the 1:n relationship between two entities. Review the mappings for the lead to contact relationship in the Default Solution in the customization area. That will show which fields in lead are mapped to which fields in contact.
ASKER
I did and the mapping is correct on both sides, lead and contact. All the other fields are passing the right data except for those 2. That is the part I don't understand. I have also deleted, re-entered, and re-mapped those two fields but they consistently move over the wrong data. For example, if one of those fields has a data set of apples, oranges, and grapes and I select grapes on the lead side, it moves over oranges. So, I know it is moving the right field over but not the right content in the field.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As per Rikin, it the option set value that is mapped not the text. It is because of these issues that I use global option sets where an option set is relevant to more than one entity,
ASKER
Thank you. The problem was that the option sets had the right defining text but the wrong line identifier and it was not matching back to the original.
Check if there is any workflow/process registered on Lead Status change. If there is any, check the update contact step.