Thursday
Hello,
I created an Import scenario for upserting lists that include account and contact information in the same sheet.
The upsert works as intended, checks for duplicate accounts and contacts, if none found creates both account and contact and links them, if account match found but no contact, creates the contact and matches to account.
Only problem i'm seeing is, if there is a duplicate contact, but no dupe account in salesforce, it will not create a new Account. I want it to still create the Account if no dupe Account is found, even if there is a dupe for the contact, and sync the contact to the new Account (we have contacts to multiple accounts enabled in SFDC).
Has anyone gotten around this before? Any advice would be greatly appreciated! Thanks
Friday
Hey @Jakewenzel - Thanks for reaching out. Good use-case discussion. Does your organization use the Account Contact Relationship (ACR) to connect contacts to multiple accounts?
Friday
Yes we do use Account Contact Relationship
Friday
Hey @Jakewenzel - You'll first want to follow the process as you showed. Next, you'll match your spreadsheet to Contacts in the Match module in order to pull in the now, corresponding Contact and Account IDs that now exist after the intial Import minus the Accounts we still need to create. Once you have that Match report, you can match against AccountContactRelation & Account, in that order. You'll want to map the corresponding IDs and Account Information necessary from our spreadsheet. We'll match to the corresponding ACR first, looking for the corresponding Account and Contact ID to match. Our ultimate goal will be in the Final Matching Conditions where we will create new accounts and check the box for Follow primary create child object selection to have the associated ACR made to the contact on your spreadsheet. Feel free to send us an email to DemandToolsCOE@validity.com if you'd like to walk through it together on a call.
Get industry news, expert insights, strategies, and hot tips, served up fresh every week.
Visit the Validity blog