This document provides detailed field mappings for integrating the Visma HR+8 system with Identum's eADM . The mappings specify how data from the source JSON files (grp_ImportHierarchy.json and emp_ImportHR.json) is processed and mapped to the corresponding fields in eADM.
The guide is divided into two main sections:
-
Department Mappings: Defines the correlation between Visma HR+8 department data and eADM unit fields.
-
User Mappings: Defines the mapping between Visma HR+8 employee data and eADM account fields.
Department Mappings
Department data is imported from the grp_ImportHierarchy.json file.
|
eADM |
Visma HR+8 Source Field |
Notes |
|
|
|
Example: |
|
|
|
Example: |
|
|
|
Example: |
|
|
|
Note: This field requires a derived value. The |
|
|
|
Example: |
|
|
|
Example: |
|
|
|
Example: |
|
|
|
Note: The original mapping considered using |
|
|
|
Example: |
User Mappings
User data is primarily imported from the emp_ImportHR.json file, with some fields originating from ImportHR.json.
|
eADM |
Visma HR+8 Source Field |
Source File |
Notes |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
The value may be |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
|
|
|
|
|
Maps from |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Note: This value should match the |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
The value may be |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Example: |
|
|
|
|
Note: You should consider using a filter to exclude closed positions from the import. |
|
|
|
|
The value may be |
|
|
|
|
Example: |
|
|
|
|
Maps from |