This is a public Forum  publicRSS

Topic

    Colin Campbell
    Mapping a Email address from a Custom Object to the...Answered
    Topic posted February 3, 2017 by Colin CampbellSpecialist 
    41 Views, 3 Comments
    Title:
    Mapping a Email address from a Custom Object to the contacts.email field
    Content:

    Hi All,

    I have a customer who has the requirement to upload external data to a custom object where the object should be associated to the main contact record.

    The object by default is related to the contacts.c_id through an association to the CO$ObjectName.Contact field.

    However the source of the data does not have the reference to the Contact ID but used the email address, is it possible to replicate this association between the CO$ObjectName.Email and contacts.email_address as the users would not be able to export the list of contacts to Excel and run a vlookup and then re-import.

    There would be no new email addresses in the source data as they will already exist in the system.

     

    Version:
    Nov 2016

    Best Answer

    Scott Harwell

    The short answer is no, you cannot a foreign key between a custom object and another object beyond the primary key(s) of the two objects.

    How many records are you considering importing?  This appears to be "stale" data, since you're not importing it into the contact object directly; a better approach would be to put this data in a DWH that can keep your legacy data separate from OSvC.  Then, when a contact is created and email address added to OSvC, you have an integration hit the DWH to see if that email address exists and then pull in the applicable data for that contact into the contact record.  OSvC custom objects are intended to be transactional and it's possible to hit performance issues if you start adding millions of records; not to mention the length of time that it will take to migrate all of the data.  So, you would want to keep those custom objects as lean as possible; also, by having the data pulled into the contact object directly gives you much more flexibility for leveraging the information (such as in Contact CPMs, rules, workspaces, etc.).

    Answer

     

    • Danette Beal

      Hi Colin,

      I'm going to move this to the general developers forum. I am not positive you can accomplish this with the import wizard and the experts on the development side should be able to guide you on what you can and cannot do with an association. 

      My two cents - my understanding is the system uses email address the unique identifier for each contact so you should be able to use that field as the reference key in an import. I do not however know how this works with a custom object.

      Good luck!

      Danette, Community Manager

    • Colin Campbell

      Thanks Danette

       

    • Scott Harwell

      The short answer is no, you cannot a foreign key between a custom object and another object beyond the primary key(s) of the two objects.

      How many records are you considering importing?  This appears to be "stale" data, since you're not importing it into the contact object directly; a better approach would be to put this data in a DWH that can keep your legacy data separate from OSvC.  Then, when a contact is created and email address added to OSvC, you have an integration hit the DWH to see if that email address exists and then pull in the applicable data for that contact into the contact record.  OSvC custom objects are intended to be transactional and it's possible to hit performance issues if you start adding millions of records; not to mention the length of time that it will take to migrate all of the data.  So, you would want to keep those custom objects as lean as possible; also, by having the data pulled into the contact object directly gives you much more flexibility for leveraging the information (such as in Contact CPMs, rules, workspaces, etc.).