Disable Auto-Populate from Parent entity RRS feed

  • Question

  • We have 4 lookup fields on a opportunity to accounts; Customer, End User, SI, and Engr Consultant.  When you create a Oppt from an account all four mapped fields are auto populated with the AccountID.  We wish to only have the Customer auto poplulated. the other three should be set by our user.  I have found the N:1 mappings but the system will not allow me to delete them.  We just want the fields to be empty when a Opportunity is created from account.

    It might be a checkbox I am missing, just cant find it. It seems to be a strange request.

    Thanks for any help,




    Friday, February 25, 2011 5:37 PM

All replies

  • Hi,

    You've stumbled across a known 'feature' unfortunately so no, you haven't missed anything. If you create several mappings between two system entities, they all get auto-mapped when you create a child record (opportunity in this case) from within the contect of the parent (account) and you cannot control this using out of the box functionality.

    See this thread for info on how to get around it.

    Hope that helps,


    Microsoft Certified Technology Specialist (CRM) GAP Consulting Ltd.
    Friday, February 25, 2011 5:57 PM
  • You're lookup fields should be built with a relationship to the User entity for those that you want to populate with a CRM user rather than a relationship to the Account entity.  You'll need to create the relationships between the Opportunity and User entity for all lookup fields except the Account field.  If you create the relationships correctly between the appropriate entities then the User related fields will not auto-populate with the Account ID.

    Regards, Donna

    Wednesday, March 2, 2011 5:47 PM
  • As mentioned you have you have stumbled upon mapping feature that is not quite consistent with the mapping methods you would expect.  So you are not missing a field or check box.   We have addressed this issue by adding a simple on load script, you will need to replace the field names with the schema names.   This script should blank out the fields.

    crmForm.all. new_ENDUSER.DataValue = null;
    crmForm.all. new_SI.DataValue = null;
    crmForm.all. new_Engr Consultant.DataValue = null;

    // do nothing



    Pierre Hulsebus - EHTC CRM Practice Manager

    Friday, March 4, 2011 4:58 AM
  • All the advice here is good and adds value so thank you very much, greatly appreciated. 

    I'm still trying to wrap my head around why we want to encourage people to build 4 relationships to the Account record when one of those relationships is for the Account record and the other 3 are for the System User entity.  This seems fairly simple to me, create one relationship with Account and the other 3 with the User entity.  The other 3 fields will not auto-populate when a new record is created and when the user does a lookup it will do the lookup on the user entity or they can populate the fields with a workflow and match the user from the related Account fields.

    In my mind, the application is working correctly and the relationships were not created in a way that supports the requirements.

    Thanks again all, have a great day!

    Regards, Donna

    Friday, March 4, 2011 2:32 PM
  • There is a quirk in the mappings of opportunity.  I don't know if it because the "Customer" field can eiter be a contact or an account.  But there is some behavior that during the on load event of a New Opportunity record if you add addiotional contact fields to the opportunity it will fille every field with the contact of the field that you created the opportunity from.  The actual mappings in the customizations have no effect on the on load behavior.     So our work arround has always been to supress the default values by a jscript that specifys the null.  

    I think in this case the  Customer, End User, SI, and Engr Consultant are not CRM User records they are Contact records that are looked up after the form is created.   So by default If I start at a contact, then load this oppotunity form up it will fill in each of these contact fields with the same contact name, the contact that is the customer value.


    Pierre - EHTC - CRM Practice manager.



    Friday, March 4, 2011 3:51 PM
  • Gotcha, thanks for taking the time to explain that, makes sense.  I made an incorrect assumption about the other fields.  They looked like they might be related to other CRM users who had a relationship with the Opportunity or played some role in it.  If the relationship is with Contact, then that clears up my confusion.

    CRMWest, does the above answer your question?  If so, please let us know.  Thank you!

    Regards, Donna

    Friday, March 4, 2011 5:39 PM