People Import Key (API)
We are migrating our email to a single domain next month. Previously, a large population (students) were on a different email domain. Student accounts are imported as customers, but we have not always set the Organizational ID for students, and Organizational ID may also be removed at some point after a student graduates. We currently have 256786 customers.
Customers do not have the following:
TeamDynamix Username
Authentication Username
Many of our customers do not have:
Organizational ID
The data that is changing for customers is Primary Email Address, which appears to be the only key remaining for an import to match.
When the email address changes on the people import file, it will most likely not match any existing customer that does not have an Organizational ID.
Is there any other way to prevent creation of duplicate customer (and potentially some user) records when the Primary Email Address is changed?
Related to a previous question: https://solutions.teamdynamix.com/TDClient/1965/Portal/Questions/Details/124574
Answer (1)
Hello Scott,
If the only field that might possibly match their account out of the 4 that we match against is the Primary Email value, and that is the same field that needs to be updated for said person, no the import would not allow their account to be updated, and any file you submitted that had different values for them for that field would just produce a second/duplicate account in your user base.
You probably would have to use the existing Primary Email on those records to first *provide* a value for them for Org ID, then you can use the Org ID to do a later import that updates their Primary Email value.