web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Field mapping not working as expected

(0) ShareShare
ReportReport
Posted on by

Hello,

 

I’ve created some custom fields on the leads and opportunity forms.

 

The custom fields for both entities are the same e.g. on the Lead I have a field called ‘Area of Interest’ with 5 option sets listed, on the opportunity record I have created the same custom field ‘Area of Interest’ with exactly the same 5 option sets listed.

 

The aim is that when a lead is qualified the opportunity record has these like for like fields already prepopulated from the Lead. I have gone in and created the relationship mappings for all these custom fields in exactly the same way.

 

The problem is only some of the fields prepopulate on the opportunity record while some do not, I can’t see anything I have done differently with the fields.

 

I’m wondering whether there is a limit on the number of fields which can be prepopulated so if the maximum limit is for example only 5 fields maximum can be prepopulated the fact that I have 8 fields explains why 3 out of the 8 fields will not automatically populate after clicking on qualify. Or maybe its something else I am doing wrong but like I say the fields are created on both the opportunity and lead with exactly the same field type, and with exactly the same values so I’m not sure what is causing this?

 

Thanks

JazB

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Haansi Profile Picture
    1,433 Moderator on at

    [quote user="JazB"]

     

    The problem is only some of the fields prepopulate on the opportunity record while some do not, I can’t see anything I have done differently with the fields.

     

    [/quote]

    Is â€˜Area of Interest’ being populated ?

    In every test same fields are not populated or different ?

    MSDN documentation does not state any limit like this. I m keen to know if there is an undocumented fact.

    There are a few other requirements for fields mapping, it can be one of these other reasons, please have this read to double check. Spacifically examing fields of both entities where mapping is not working.  

    You can do a test, just map a few fields which are not working previously and ignore those working fine, result will clarify it. But again it can be one of the reasons described in this article.

  • Community Member Profile Picture
    on at

    Hi Yawer,

    After reading the link I now see what the problem was, I obviously did not enter the option set labels in the same order for each entity, therefore the values were different and the auto prepopulating would not work even though the fields were mapped.

    I have changed this now so that labels and values are exactly the same for each entity and this seems to have solved the issue.

    Thank you for your help.

    JazB

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans