Nice IEX Orgdata Tips
|Software product name||Skills Mangement|
|Version Number||8.5.x and Above|
|Subject||Nice IEX Orgdata Tips|
- WFM users not being imported by Orgdata.
- Agents not being Placed under their Manager in the User Hierarchy
- User data missing from import
WFM users not being imported by Orgdata
In order for Orgdata to pull user data from NICE IEX WFM the User must have the following Agent Data Groups (ADGs) or Agent Data Values (ADVs) if these are missing or not unique Orgdata may see the User an invalid and remove them from the import:
- Skills Manager Role
- This is a custom ADG that is used to identify Users that are Trainers, Managers or Agents
- Managers ID
- This ADG is used to store the User's Line Manager's Employee ID. We use this to map Users to their Manager when creating the reporting hierarchy.
- This should be populated and unique as it is typically used as a key field when mapping Users within the system.
- MU Name
- MU Name can be collated as a standard Orgdata field. This can be very useful when filtering the Users to be imported as custom scripts can be used to remove specific MU's from the import data.
Agents not being Placed under their Manager in the User Hierarchy
There are 3 possible causes of User Hierarchy not being built correctly:
- The LMPositionID field in Orgdata is not mapped to the WFM User field that contains the Agent's Manager's Employee ID.
- The PositionID field in Orgdata is not mapped to a field that contains a unique value.
- WFM has not had the Manager's Employee ID entered against the Agent in the correct ADG.
User data missing from import
The most common cause for missing data is a mismatch in the mapping of the Orgdata fields with WFM. Most issues can be resolved by checking the field/column names in the Orgdata Config XML for spelling and formatting errors such as:
- "'EmployeID'" rather than "'EmployeeID'"
- "'LeadEmploymentID'" rather than "'Lead Employment ID'"
When mapping Orgdata fields to WFM User data fields the field/column names must match exactly. Some WFM ADGs may contain spaces or special characters.
- Employee ID is mandatory and must be unique, if duplicates are found the Orgdata process will stop and the import will fail.
- ADG can often have a rouge <space> at the beginning or end of the name causing a mapping mismatch.
- When creating the Import Template the field that maps to LoginID must contain unique values. Duplicates will cause the push of data to Performance DNA to fail.
Sample Orgdata Config file Mapping
<ImportSources CsvFilePath="" BackupFilePath="" PostImportSql=""> <Source Type="Wfm" ID="1" MergeMethod="Append"> <Mapping Field="Username" WfmField="EmployeeId" /> <Mapping Field="EmployeeID" WfmField="EmployeeId" IsKey="true" /> <Mapping Field="PositionID" WfmField="EmployeeId"/> <Mapping Field="WfmUserId" WfmField="UserId" /> <Mapping Field="FirstName" WfmField="FirstName" /> <Mapping Field="LastName" WfmField="LastName" /> <Mapping Field="Email" WfmField="Email" /> <Mapping Field="LMPositionID" WfmField="Team Manager ID" /> <Mapping Field="Site" WfmField="Site" /> <Mapping Field="Team" WfmField="Team" /> <Mapping Field="TrainingPlannerRole" WfmField="Training Planner Role" />