locked
Parent Customer not populated in Contact when Contact created from Primary Contact field on Account form RRS feed

  • Question

  • Hi,

    I have found this to be true in several environments I have tested...just checking to see if I have missed something, or if this is they way it is supposed to work:

    If you:

    Create a new Account Record

    On the Account Form, click the spyglass for Primary Contact

    Create a new Contact and select it for the Primary Contact of the new Account

    Save

    The Primary Contact in the Account record is properly updated

    however.... the new contact record you just created and added as the Primary Contact for the Account  .. does not have the Account in the Parent Customer field.

     

    I know the Parent Customer is updated properly in the Contact record if you create the Account, click on Contacts and new.  But, if you create the Contact from the Primary Contact on Account form, it isn't.

    I put a simple workflow in place to update the Parent Customer for the scenario above, just wondered if this is just how it works, or if there is a setting somewhere I have missed.

    Have a great day!

    Voni


    Voni Garrett
    Tuesday, November 8, 2011 5:54 PM

Answers

  • I think this the correct function, since what happens when you set the "Parent Customer" on the contact form (in the case it is an account) you will be able to see that person under the navigation item on the account form under Common->Contacts, if the "Parent Customer" is a contact you should be able to see that person on the Contact form under the navigation item under Common->Sub-Contacts.

     

    To the best of my knowledge the Parent Customer field on the contact form and the  Primary Contact are not related, this is why they do not get updated from each others data.

    Just as if you were to create one to many relationship for any entity you will always get a lookup item on one side and a navigation item on the other side, not a lookup field on both forms.


    Halldór Jóhannsson
    • Marked as answer by vonig Thursday, November 10, 2011 4:55 PM
    Wednesday, November 9, 2011 9:59 AM
  • This is how it suppose to work. There are two different fields.

    1.  There is 1:N relationship between account and contact(Parent Customer relationship), if you create a child entity from parent, it will map the parent reference in the child record. That's why it works.
    2. The primary contact relationship between account to contact is N:1, so mapping won't work.

         In short mapping work if you create a child from parent.

    In crm primary contact does not have to be the same account's contact. It can belong to any other account in the system.

    I hope this help.


    Amreek Singh Senior CRM Consultant CDC Praxa Sydney, Australia http://mscrmshop.blogspot.com http://crm2011usersettings.codeplex.com

    • Edited by Amreek Singh Wednesday, November 9, 2011 10:15 AM
    • Proposed as answer by Amreek Singh Wednesday, November 9, 2011 10:15 AM
    • Marked as answer by vonig Thursday, November 10, 2011 4:55 PM
    Wednesday, November 9, 2011 10:12 AM

All replies

  • I think this the correct function, since what happens when you set the "Parent Customer" on the contact form (in the case it is an account) you will be able to see that person under the navigation item on the account form under Common->Contacts, if the "Parent Customer" is a contact you should be able to see that person on the Contact form under the navigation item under Common->Sub-Contacts.

     

    To the best of my knowledge the Parent Customer field on the contact form and the  Primary Contact are not related, this is why they do not get updated from each others data.

    Just as if you were to create one to many relationship for any entity you will always get a lookup item on one side and a navigation item on the other side, not a lookup field on both forms.


    Halldór Jóhannsson
    • Marked as answer by vonig Thursday, November 10, 2011 4:55 PM
    Wednesday, November 9, 2011 9:59 AM
  • This is how it suppose to work. There are two different fields.

    1.  There is 1:N relationship between account and contact(Parent Customer relationship), if you create a child entity from parent, it will map the parent reference in the child record. That's why it works.
    2. The primary contact relationship between account to contact is N:1, so mapping won't work.

         In short mapping work if you create a child from parent.

    In crm primary contact does not have to be the same account's contact. It can belong to any other account in the system.

    I hope this help.


    Amreek Singh Senior CRM Consultant CDC Praxa Sydney, Australia http://mscrmshop.blogspot.com http://crm2011usersettings.codeplex.com

    • Edited by Amreek Singh Wednesday, November 9, 2011 10:15 AM
    • Proposed as answer by Amreek Singh Wednesday, November 9, 2011 10:15 AM
    • Marked as answer by vonig Thursday, November 10, 2011 4:55 PM
    Wednesday, November 9, 2011 10:12 AM
  • Thank you for verifying for me!
    Voni Garrett
    Thursday, November 10, 2011 4:56 PM
  • Thank you for verifying for me!
    Voni Garrett
    Thursday, November 10, 2011 4:56 PM
  • You are quite welcome 8)
    Halldór Jóhannsson
    Friday, November 11, 2011 9:10 AM