We are already running into the same issue and this would help. To be honest, most of the contact data we get has an account name but partial and we really need to try and match that account name up to something in the system to set that account ID/name when loading the contact data. I agree- we shouldn't need multiple tools to do this. I am jumping on a call thursday and will post if I find a way to do this.
Hi Aric,
Any update from your meeting?
Thanks!
Pam
They have a tool being developed that is close to going into testing that could help with this. I think its specific to loading a row of data that has both the account and contact in it so we can make the account first and then auto associate the contact with that account. I don't know much more. I'll be curious how it handles like finding a duplicate account and adding that back into step two of creating the contact.
Pamela Giovanelli
Hi there,
There appear to be a limited number of account fields available to map to when importing a file of contacts. I don't always have the account_id, instead having to map on a custom identifier (in this case the unit_id__c field which is a variable assigned by IPEDS). So, right now (unless I'm mistaken), for matching rule to find existing contacts, I'll first have to match on the account name from my source file to SF (which is always fun) or use Snowflake to find the matches and then export that file, or use your software to first find the accounts then pull the files together.. That's a multi-step process that I shouldn't have to go through.
Thanks!
1 person likes this idea