Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Editing field options on forms RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All

    I hope you can help me.

    We have two separate entities called Opportunities and Leads. Both forms have a field called Vendor. I've added a new vendor to the options list of this field and manually assigned it a value. I'm just curious, do I have to to manually add this vendor to the Leads entity also? The Vendor options list in both leads and Opportunities are the same and it looks like each option has the same value. If I add the same vendor and value to Leads will they be linked? We do also have Accounts for each vendor, however I'm not really sure that they are linked to the options in Opportunities and Leads.

    I hope my question makes sense.

    Thanks

    Linden

    Monday, April 22, 2013 4:51 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Linden,

    No! It is not necessary to add the option to both of the entities. But, if you want to have consistent data you have to map them. I mean that, for example on a Lead you have the option A' but on the Opportunities you do not have the A' option. Hence, when you create an opportunity from a lead you do not have this option to select or map.

    To have consistent data, create the similar option for both entities. To map them go to settings > customizations > customize the system > entities > lead > 1:N relations > find the relation with opportunities. Then create a mapping between these two option sets.


    My Weblog -- My Website

    Monday, April 22, 2013 5:08 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    About this, you could have two solutions:

    1- Using global option sets. Create a global option set and use it on required entities such as account, lead and opportunity.

    2- Using local options sets for each of the entities.

    In my opinion, using global option sets are better, and maintains the data consistency. To ensure that you do not loss the data, use mapping on the relationships (as mentioned above). This enables you to set the value of the option set on the opportunity from the lead on the creation of the opportunity.

    About the replies, some experts helped me before this to solve my problems. Hence, I have to help others to solve their problems. :)


    My Weblog -- My Website

    Tuesday, April 23, 2013 12:16 PM
    Moderator

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Linden,

    No! It is not necessary to add the option to both of the entities. But, if you want to have consistent data you have to map them. I mean that, for example on a Lead you have the option A' but on the Opportunities you do not have the A' option. Hence, when you create an opportunity from a lead you do not have this option to select or map.

    To have consistent data, create the similar option for both entities. To map them go to settings > customizations > customize the system > entities > lead > 1:N relations > find the relation with opportunities. Then create a mapping between these two option sets.


    My Weblog -- My Website

    Monday, April 22, 2013 5:08 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Payman

    Thanks for your response.

    That makes sense. I'm just wondering, I had created a previous vendor in the entity 'Opportunity' and not in 'Leads'. It's been used for a number of weeks now. Is there anyway that I can map this to  Leads or should the relationship only be from Leads to Opportunity?

    I'm also wondering if the Vendor I created in Accounts should also be mapped somehow to Leads and Opportunities or perhaps this is separate?

    Thanks

    Linden

    Tuesday, April 23, 2013 10:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It is obvious that mapping from opportunity to lead is not so logical. Because you create opportunities from the leads and not the leads from opportunities. About the account, you could map it to the lead.


    My Weblog -- My Website

    Tuesday, April 23, 2013 11:27 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    So that leaves me with one query. For the Vendor that I have already added in Opportunities, how can I add the same Vendor in Leads, but at the same time ensure that the Lead can be converted into an Opportunity? I just want to make sure that there is no loss of data. Is this possible having already created the Vendor as an option in Opportunity?

    By the way thanks for your help on this. It's been extremely helpful!

    Lindt

     
    Tuesday, April 23, 2013 11:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    About this, you could have two solutions:

    1- Using global option sets. Create a global option set and use it on required entities such as account, lead and opportunity.

    2- Using local options sets for each of the entities.

    In my opinion, using global option sets are better, and maintains the data consistency. To ensure that you do not loss the data, use mapping on the relationships (as mentioned above). This enables you to set the value of the option set on the opportunity from the lead on the creation of the opportunity.

    About the replies, some experts helped me before this to solve my problems. Hence, I have to help others to solve their problems. :)


    My Weblog -- My Website

    Tuesday, April 23, 2013 12:16 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Payman!

    I've used some of the solutions above :)

    Thursday, April 25, 2013 2:26 PM