- PERSON_ID_EXTERNAL appears in basic user import file, although I don't see it listed in the standard element in Manage Business Config
- We've noticed a new column in the basic user import file PERSON_ID_EXTERNAL. What's it for?
Employee Central 2.0
Reproducing the Issue
Download Basic User Info Import Template
See new column PERSON_ID_EXTERNAL
In order to provide a possibility to pass over a GUID from outside (e.g if the source system already supports the concept of a global, unique identifier) we have to expose PERSON_GUID and PERSON_ID_EXTERNAL as new parameters in basic user import.
Reasoning behind this:
Often customers will create users in the system, and have the system create these users with an automatically generated user system ID. Later they reaslise that they need to maintain a Global User ID for that user as part of a 3rd party integration.
For EC customers, they can use the Person Id External value in the Person Info Element, but for non-EC customers, this was not possible. Now with the Person Id External value being maintained in the Basic User Import file, you can add a backend Person Id External value to a user account which can help identify users as part of a 3rd party integration.
The Field is a DB field, and is not exposed in the User Profile Page in Front End of system.
This value should only be imported for Non-Ec customers using the basic user improt. For Ec customers integrations should be set up to target the Person_Id_External field in the Biographical Information (personInfo) portlet/element.
basic user file, basic user file import template, person-id-external, person id external, Person_Id_external, UDF, User Directory File , KBA , LOD-SF-PLT , Foundational Capabilities & Tools , LOD-SF-EP , Employee Profile , LOD-SF-EC-EDP , Employee Data Imports , Problem