Not sure if it is the same issues, but lately I am having some imports that for some reason changes the last name... and also the import mapping is correct. Let's see if someone has some input...
What is your data source? (LDAP/CSV/XML etc.)can you provide screen shots or example data and your mapping?
1 of 1 people found this helpful
I had a look at the business rules and there was a trigger action which was linking a manager to an employee. This was a search and link. This was the root cause of this issue.
Well that is a clue, I will look into that too!
Thank you for asking, we use a .csv file, but I have been looking ingot it and my "unique" filed... it is not as unique as I expected probably the cause. I will clean up the file and ask again if the issue stays!
Yes. Just have a look at all the business rules in the Employee or Frs Composite Contact Objects.
Essentially don't import the Display Name field it is a calculated field, the calculation is a business rule on the employee object. You can change the rule if you don't like the format for example removing the Middle Name.
Calculation Rule for Employee.DisplayNameDisplayName
$(Trim(nvl(FirstName, "") + " " +
(if nvl(MiddleName, "") == "" then "" else MiddleName + " ") +
Yes, thank you, in my case the import is changing the last name, and that is why the Display Name changes.
But good point!