ACCT/DEPT name change and nightly import
I changed the name of an ACCT/DEPT because it was changed at the organizational level and was reflected in our nightly data feed for a couple of customers.
After the name change in TD, I'm still seeing an error on the import job that the <new name> "is not a valid choice for the "Acct/Dept" property."
I've never had an issue with the import associating users after creating a new ACCT/DEPT after seeing the error in the import job.
Thoughts or places I should be looking? I copied the name from the Import Job error to use when editing the entry. Both of the customers impacted have the new acct/dept name listed for them, so there should be nothing to update anymore.
Thanks,
Pam Jordan
Answer (1)
Hello Pamela,
I'd have to have a copy of the actual import file that was sent, and know which user/users were affected in particular to better troubleshoot this.
Since that is likely fairly sensitive in nature, you might wish to open a support ticket and provide that file on the ticket so it isn't in this public forum for all to see.
Sincerely,
Mark Sayers
Sr Support Consultant, CS
It only impacts two customers, but I'll ask for a copy of the import file in case there's anything obvious in the raw data.
If I don't see anything, I'll submit a ticket and include the data file.
-Pam - Pamela Jordan Wed 4/5/23 10:59 AM