Field Mapping - value from source field does not appear in target field

(0) Share

Report

Posted on by Jea2nie

720

Hi,

I have created a gender field in my Lead Entity and map that as the source to the target field, Gender, in the Contact Entity. The value of gender in Lead Entity should be transferred the the gender field in Contact Entity when the Lead is Qualified and the Contact record is created.

I have published the customisation but for some strange reason the Gender field value does not appear in Contact gender field. And I did not received an error message as well. I checked that the format of both fields is the same. The only difference that I can find is the value of the option sets is different. Male=1, Female=2 in Gender field in Contact and Male=100,000,000 and Female=100,000,001 in Lead. Is this why it didn't work?

I do not dare to change the value in Lead as I received the warning that "Existing records and customizations might reference this option value. Those references will not be updated if this option value is changed. Do you want to continue?". I don't really understand this warning, not sure what is the impact if I change it.

Or is there any other possibility why my field mapping didn't work?

Cheers,
Jeannie

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (3)

Verified answer

CRMInnovation.com on at

Like (0)

Report

Jeannie,

Starting with the last point first. Yes if you change the value in leads, which is how the data is stored, you will loose access to the records with a value of 1.

On the mapping, you should go into the Contact field and change the values to 100,000,000 and 100,000,001 accordingly.

Then the mapping should work.

Was this reply helpful? Yes No
Jea2nie 720 on at

Like (0)

Report

Thanks Jerry.

We have a policy to try not change the default settings of CRM as we cannot see the impact of change. I ended up creating another gender field in the Contact field and hide the CRM default gender field.

Was this reply helpful? Yes No
Verified answer

Hosk on at

Like (0)

Report

The mapping on optionsets works using the values not the labels.

CRM is trying to map the values but cannot find a value to map because the optionset numbers are different.

You need to change the gender field on the contact to have the same values as the lead and then it will work

Was this reply helpful? Yes No
Hosk on at

Like (0)

Report

if Jerry helped you resolve the problem please mark his answer as the suggested answer

Was this reply helpful? Yes No
Verified answer

Rugved Gokhale on at

Like (0)

Report

Hi,

Its true that such mapping works on value part & not label part. So your existing option sets can't be used directly for this auto-mapping and its also very risky to change the value part of existing labels as there could be some plugin/JS based logic working on it which will fail afterwards.

But you can create a new copy of this gender option set & treat this new field as dummy & keep it hidden from users. So user's won't feel any difference. Then you can design a workflow which will trigger on contact create & set this old Gender based on new dummy gender. Here, your dummy gender field will be mapped with lead as it is having same value part.

I would not recommend real time WF here as in this case, contact will be created in context of Lead qualification process & not independent contact creation process. So could not guarantee RTWF's exact behaviour here. So its better to go for background WF.

Using WF is the code less solution here. But if you have technical expertise, having this done in plugin will give you quickest response.

So idea here is to add additional indirect linkage which will change your gender attribute on contact.

Hope this helps.

Was this reply helpful? Yes No
Jea2nie 720 on at

Like (0)

Report

Hi,

I created try to create the same value for gender field in Lead as the gender field in contact (default value).

CRM wouldn't let me do it. Said the value has been used before.

Therefore I opted to create a dummy field in contact and created a background WF to copy the value to the default gender field. Not the most beautiful workaround, but it works.

Thanks,

Jeannie

Was this reply helpful? Yes No