none
A question about Fields in Leads vs Opportunity Entity

    Question

  • Ok... so I have a question, and I am hoping someone here can help. It's apparently so basic that everyone else knows how to do this, but despite pouring through dozens of YouTube pages and websites, I simply cannot figure this out.

    So....here it is: Let's say we need to add three custom fields (Facebook, Twitter, LinkedIn) to the Lead Entity, so that these fields can be edited on the Lead Form.

    • When the Lead converts to an Opportunity, now the company info shifts to the "Opportunity" entity.
    • We want the 3 custom fields (from the Lead entity) to be visible ** - and editable - ** on the Opportunity Form. How the heck do you do that?


    We figured out how to use QuickView to make the fields visible, but that doesn't really help. And bouncing around all these pages to do simple data entry and updates is a beating.

    Thanks in advance for any help!

    Thursday, March 16, 2017 4:59 PM

All replies

  • Hi,

    You can utilise the field mappint capability of dynamics CRM. Once you have created the fields in Opportunity in CRM you need to go to the relevant Lead-Opportunity relationship and map these fields .Check the below post:

    http://crm.fullscope.com/save-time-entering-data-into-crm-by-mapping-fields-between-records/

    Thanks


    Sachith Chandrasiri

    Thursday, March 16, 2017 10:20 PM
  • Thank you! I am reading the link now and I think that is the solution I am looking for.

    Just for clarification... this will make fields from Entity 1 to be editable in Forms from Entity 2, right?

    For example, lets say I am looking at the Opportunity Form and I want to add/edit the phone number or email for the Primary contact. This will help me make the Contact Info fields to be editable when viewing the Opportunity Form?

    Thursday, March 16, 2017 10:37 PM
  • Wow... after reading thru this, I'm not sure this is right or not.

    There are some slight GUI differences in this version (I assume 2011) and the one we are using (2016).... but basically what it looks like CRM is doing is forcing you to create the same field in two different places (Entities, in this case), then its linking the two fields together.

    I am not entirely sure... the Use Case presented in this walk-thru is more about creating Parent-Child records, which is not what we are needing to do.
    Thursday, March 16, 2017 10:49 PM
  • Well if you create those contact info fields on the opportunity entity and map those contact info fields too you can edit them in Opportunity form. But editing them in Opportunity form will not go and update those in Contact record. Field mapping loads data intilally from the parent entity and after that there is no link. To achieve this you will have to write custom code like a plugin.

    Sachith Chandrasiri

    Thursday, March 16, 2017 10:55 PM