This document provides a detailed description of the fields in the XML master data file that is imported from Unit4 Agresso. It is intended for technical personnel responsible for setting up and maintaining the integration.
The import consists of two main parts: Employee Data and Organizational Hierarchy.
Employee Data
Employee data contains information about individual users, their contact details, and their various employment records.
Example of Employee Data
Below is an example snippet of the
element for a single employee in the XML file.
XML
64699
1
Høneveien 17
Utfjord
NO
4000
ola.nordmann@utfjord.kommune.no
2016-02-26T08:55:58
9002
A
Fast
true
100
Annet
691204
Driftsoperatør
1996-01-01
4.1
4098
0
Teknisk anlegg vann og avløp
2023-05-01
2099-12-31
5312
B
Tekniske va-anlegg
2023-04-01
2099-12-31
35,5
35.5
35,5 t pr. uke
2023-05-01
2099-12-31
2023-05-01
2099-12-31
L1
514264
2016-03-01
2099-12-31
Ola
Nordmann
Nordmann, Ola
OLANORD
1
1978-05-15
00000000000
M
3487
N
OLANORD
offsam\olanord
514264
Employee Field Descriptions
XML Path: Address/Street | Description: Street address. | Data Type: String | Mandatory: No | Usage: Not used.
XML Path: Address/Place | Description: City or town. | Data Type: String | Mandatory: No | Usage: Not used.
XML Path: Address/ZipCode | Description: Postal code. | Data Type: Integer | Mandatory: No | Usage: Not used.
XML Path: Address/mobile | Description: Mobile phone number. | Data Type: Integer | Mandatory: No | Usage: Used in notification flows for onboarding and offboarding.
XML Path: Address/eMailList/string | Description: Email address. | Data Type: String | Mandatory: No | Usage: Used in notification flows for onboarding and offboarding.
XML Path: employments/employment@resourceID | Description: Employee number. | Data Type: Integer | Mandatory: Yes | Usage: Uniquely identifies the employee within the company.
XML Path: employments/employment/employmentType | Description: Employment category code (e.g., 'F' for 'Fast'). | Data Type: String | Mandatory: No | Usage: Used for messaging, user account management, and access control.
XML Path: employments/employment/EmploymentTypeDescription | Description: Description of the employment category (e.g., 'Fast'). | Data Type: String | Mandatory: No | Usage: Used for messaging, user account management, and access control.
XML Path: employments/employment/MainPosition | Description: Indicates if this is the employee's primary position (true/false). | Data Type: String | Mandatory: No | Usage: Used for messaging, user account management, and access control.
XML Path: employments/employment/Percentage | Description: Position percentage (e.g., 100). | Data Type: Integer | Mandatory: No | Usage: Used for messaging, user account management, and access control.
XML Path: employments/employment/PostId | Description: Position Code ID. | Data Type: Integer | Mandatory: No | Usage: Used for messaging, user account management, and access control.
XML Path: employments/employment/PostIdDescription | Description: Position title. | Data Type: String | Mandatory: No | Usage: Used for messaging, user account management, and access control.
XML Path: employments/employment/PostCode | Description: Position code. | Data Type: String | Mandatory: No | Usage: Used for messaging, user account management, and access control.
XML Path: employments/employment/PostCodeDescription | Description: Work type description. | Data Type: String | Mandatory: No | Usage: Used for messaging, user account management, and access control.
XML Path: employments/employment/Relation/Value | Description: Department/responsibility ID. See ElementType attribute. | Data Type: String | Mandatory: No | Usage: Used to link users to departments and responsibilities for access control and messaging.
XML Path: employments/employment/Relation/Description | Description: Department/responsibility name. | Data Type: String | Mandatory: No | Usage: Used to display which department and responsibility the user belongs to.
XML Path: employments/employment/DateFrom | Description: Start date for the specific position. | Data Type: Date | Mandatory: No | Usage: Used for access control and to activate/deactivate user accounts.
XML Path: employments/employment/DateTo | Description: End date for the specific position. | Data Type: Date | Mandatory: No | Usage: Used for access control and to activate/deactivate user accounts.
XML Path: DateFrom | Description: Start date for the entire employment relationship. | Data Type: Date | Mandatory: Yes | Usage: Used for access control and to activate/deactivate user accounts.
XML Path: DateTo | Description: End date for the entire employment relationship. | Data Type: Date | Mandatory: No | Usage: Used for access control and to activate/deactivate user accounts.
XML Path: FirstName | Description: First name. | Data Type: String | Mandatory: Yes | Usage: Used in notification flows.
XML Path: Surname | Description: Last name. | Data Type: String | Mandatory: Yes | Usage: Used in notification flows.
XML Path: ShortName | Description: Short name or username alias. | Data Type: String | Mandatory: No | Usage: Can be mapped to sAMAccountName in a local Active Directory.
XML Path: SocialSecurityNumber | Description: Norwegian national identity number. | Data Type: String | Mandatory: Yes | Usage: Uniquely identifies the employee across systems, including Feide.
XML Path: user/UbwUserID | Description: User ID from Unit4 Business World. | Data Type: Integer | Mandatory: No | Usage: Uniquely identifies the employee for write-back operations to U4BW.
XML Path: user/DomainInfo | Description: Registered username in U4BW (e.g., domain\username). | Data Type: String | Mandatory: No | Usage: Compared with sAMAccountName in Active Directory.
XML Path: user/resourceID | Description: Employee number. | Data Type: Integer | Mandatory: Yes | Usage: Uniquely identifies the employee for write-back operations to U4BW.
Note: A user can have multiple
nodes, one for each position they hold. Users without an active position will appear in the master data file without an
node. Likewise, a user can have multiple
nodes per position.
Organizational Hierarchy
This part of the file defines the organizational structure, including departments and their relationships.
Example of Organizational Data
Below is an example snippet of an
element.
XML
L1
Utfjord ungdomsskole
5003
4014
503579
0001-01-01T00:00:00
9999-12-31T23:59:59.9999999
2016-01-13T12:54:14
N
Organizational Field Descriptions
XML Path: CompanyCode | Description: Company code. | Data Type: Text | Mandatory: Yes | Usage: Used to build the organizational hierarchy.
XML Path: Name | Description: Department name. | Data Type: Text | Mandatory: Yes | Usage: Used to build the organizational hierarchy.
XML Path: Id | Description: Department ID. | Data Type: Number | Mandatory: Yes | Usage: Uniquely identifies the department.
XML Path: ParentId | Description: ID of the parent department. | Data Type: Number | Mandatory: Yes | Usage: Uniquely identifies the parent department to build the hierarchy.
XML Path: Managers/string | Description: ID of the department manager. | Data Type: Number | Mandatory: Yes | Usage: Sets the department manager, used for access control and onboarding/offboarding notifications.
XML Path: DateFrom | Description: Date the department is valid from. | Data Type: Date | Mandatory: No | Usage: Used to activate/deactivate departments.
XML Path: DateTo | Description: Date the department is valid to. | Data Type: Date | Mandatory: No | Usage: Used to activate/deactivate departments.
XML Path: LastUpdate | Description: — | Data Type: Date | Mandatory: No | Usage: Used to activate/deactivate departments.
XML Path: Status | Description: Status of the department (e.g., 'A' for Active). | Data Type: Text | Mandatory: No | Usage: Used to activate/deactivate departments.