If the admin perform Merge or copy of the user, the old user external id will be copied to the new users external id only in situation where New user External ID is "Null". Please find the example below for old external id after Copy user.
Overview of the new functionality External id :
--> From 1611 onwards, when we copy a user- the copied user (new user) will retain the external ID of the Old user external ID- in any case we won’t be seeing it as blank , The external id should be same as user id.
--> If there any user ID’s left out with no external IDs in 1608, during the 1611 – the upgrader script will run to populate the external ID’s to match the user ID’s
--> Copying the old external ID might be the behavior in the short-term, but that’s not how it’s going to work in the long-term. External IDs have to be unique.
Learning Management System
Reproducing the Issue
perform copy or merge user to get old external id to the new user.
To update the external id of the newly copied user, admin should run user connector with the 'PERSON_ID_EXTERNAL' filed in the feed file with new user id as external id. Below is the sample feed format.
After connector run the old external id of the merge user will be updated with the new external id.
externalID , Merge , copy user , external ID. , KBA , LOD-SF-LMS , SuccessFactors Learning , Problem