Duplicate of Guide to Unit4 Agresso Data Import

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 <Resource> element for a single employee in the XML file.

CODE

XML

CODE

<Resource>
    <Addresses>
        <Address>
            <AddressId>64699</AddressId>
            <Type>1</Type>
            <Contact />
            <Position />
            <Street>Høneveien 17</Street>
            <Place>Utfjord</Place>
            <Province />
            <CountryCode>NO</CountryCode>
            <ZipCode>4000</ZipCode>
            <Telephone />
            <Telefax />
            <Telex />
            <Mobile />
            <Pager />
            <Home />
            <Assistant />
            <EMailList>
                <string>ola.nordmann@utfjord.kommune.no</string>
            </EMailList>
            <EMailCopyList>
                <string />
            </EMailCopyList>
            <LastUpdate>2016-02-26T08:55:58</LastUpdate>
        </Address>
    </Addresses>
    <Employments>
        <Employment ResourceId="514564">
            <PostId>9002</PostId>
            <EmploymentType>A</EmploymentType>
            <EmploymentTypeDescription>Fast</EmploymentTypeDescription>
            <MainPosition>true</MainPosition>
            <Percentage>100</Percentage>
            <PostIdDescription>Annet</PostIdDescription>
            <PostCode>691204</PostCode>
            <PostCodeDescription>Driftsoperatør</PostCodeDescription>
            <SeniorityDate>1996-01-01</SeniorityDate>
            <WageRule>4.1</WageRule>
            <Relations>
                <Relation Type="MNAL" Name="Organisasjonstilhørighet" ElementType="ORGANISATION">
                    <Value>4098</Value>
                    <Value1>0</Value1>
                    <Description>Teknisk anlegg vann og avløp</Description>
                    <DateFrom>2023-05-01</DateFrom>
                    <DateTo>2099-12-31</DateTo>
                </Relation>
                <Relation Type="C1" Name="Ansvar" ElementType="COST_CENTER">
                    <Value>5312</Value>
                    <Value1>B</Value1>
                    <Description>Tekniske va-anlegg</Description>
                    <DateFrom>2023-04-01</DateFrom>
                    <DateTo>2099-12-31</DateTo>
                </Relation>
                <Relation Type="MNBB" Name="Arbeidstid pr. uke" ElementType="WORK_TIME_GROUP">
                    <Value>35,5</Value>
                    <Value1>35.5</Value1>
                    <Description>35,5 t pr. uke</Description>
                    <DateFrom>2023-05-01</DateFrom>
                    <DateTo>2099-12-31</DateTo>
                </Relation>
            </Relations>
            <DateFrom>2023-05-01</DateFrom>
            <DateTo>2099-12-31</DateTo>
        </Employment>
    </Employments>
    <CompanyCode>L1</CompanyCode>
    <ResourceId>514264</ResourceId>
    <DateFrom>2016-03-01</DateFrom>
    <DateTo>2099-12-31</DateTo>
    <FirstName>Ola</FirstName>
    <Surname>Nordmann</Surname>
    <Name>Nordmann, Ola</Name>
    <ShortName>OLANORD</ShortName>
    <ResourceType>1</ResourceType>
    <Birthdate>1978-05-15</Birthdate>
    <SocialSecurityNumber>23027844556</SocialSecurityNumber>
    <Sex>M</Sex>
    <Municipal>3487</Municipal>
    <Status>N</Status>
    <User>
        <UbwUserId>OLANORD</UbwUserId>
        <DomainInfo>offsam\olanord</DomainInfo>
        <ResourceId>514264</ResourceId>
    </User>
</Resource>

Employee Field Descriptions

XML Path	Description	Data Type	Mandatory	Usage
`Address/Street`	Street address.	String	No	Not used.
`Address/Place`	City or town.	String	No	Not used.
`Address/ZipCode`	Postal code.	Integer	No	Not used.
`Address/mobile`	Mobile phone number.	Integer	No	Used in notification flows for onboarding and offboarding.
`Address/eMailList/string`	Email address.	String	No	Used in notification flows for onboarding and offboarding.
`employments/employment@resourceID`	Employee number.	Integer	Yes	Uniquely identifies the employee within the company.
`employments/employment/employmentType`	Employment category code (e.g., 'F' for 'Fast').	String	No	Used for messaging, user account management, and access control.
`employments/employment/EmploymentTypeDescription`	Description of the employment category (e.g., 'Fast').	String	No	Used for messaging, user account management, and access control.
`employments/employment/MainPosition`	Indicates if this is the employee's primary position (`true`/`false`).	String	No	Used for messaging, user account management, and access control.
`employments/employment/Percentage`	Position percentage (e.g., 100).	Integer	No	Used for messaging, user account management, and access control.
`employments/employment/PostId`	Position Code ID.	Integer	No	Used for messaging, user account management, and access control.
`employments/employment/PostIdDescription`	Position title.	String	No	Used for messaging, user account management, and access control.
`employments/employment/PostCode`	Position code.	String	No	Used for messaging, user account management, and access control.
`employments/employment/PostCodeDescription`	Work type description.	String	No	Used for messaging, user account management, and access control.
`employments/employment/Relation/Value`	Department/responsibility ID. See `ElementType` attribute.	String	No	Used to link users to departments and responsibilities for access control and messaging.
`employments/employment/Relation/Description`	Department/responsibility name.	String	No	Used to display which department and responsibility the user belongs to.
`employments/employment/DateFrom`	Start date for the specific position.	Date	No	Used for access control and to activate/deactivate user accounts.
`employments/employment/DateTo`	End date for the specific position.	Date	No	Used for access control and to activate/deactivate user accounts.
`DateFrom`	Start date for the entire employment relationship.	Date	Yes	Used for access control and to activate/deactivate user accounts.
`DateTo`	End date for the entire employment relationship.	Date	No	Used for access control and to activate/deactivate user accounts.
`FirstName`	First name.	String	Yes	Used in notification flows.
`Surname`	Last name.	String	Yes	Used in notification flows.
`ShortName`	Short name or username alias.	String	No	Can be mapped to `sAMAccountName` in a local Active Directory.
`SocialSecurityNumber`	Norwegian national identity number.	String	Yes	Uniquely identifies the employee across systems, including Feide.
`user/UbwUserID`	User ID from Unit4 Business World.	Integer	No	Uniquely identifies the employee for write-back operations to U4BW.
`user/DomainInfo`	Registered username in U4BW (e.g., `domain\username`).	String	No	Compared with `sAMAccountName` in Active Directory.
`user/resourceID`	Employee number.	Integer	Yes	Uniquely identifies the employee for write-back operations to U4BW.

Note: A user can have multiple <Employment> nodes, one for each position they hold. Users without an active position will appear in the master data file without an <Employment> node. Likewise, a user can have multiple <Relation> 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 <Organisation> element.

CODE

XML

CODE

<Organisation>
    <CompanyCode>L1</CompanyCode>
    <Name>Utfjord ungdomsskole</Name>
    <Id>5003</Id>
    <ParentId>4014</ParentId>
    <Managers>
        <string>503579</string>
    </Managers>
    <DateFrom>0001-01-01T00:00:00</DateFrom>
    <DateTo>9999-12-31T23:59:59.9999999</DateTo>
    <LastUpdate>2016-01-13T12:54:14</LastUpdate>
    <Status>N</Status>
</Organisation>

Organizational Field Descriptions

XML Path	Description	Data Type	Mandatory	Usage
`CompanyCode`	Company code.	Text	Yes	Used to build the organizational hierarchy.
`Name`	Department name.	Text	Yes	Used to build the organizational hierarchy.
`Id`	Department ID.	Number	Yes	Uniquely identifies the department.
`ParentId`	ID of the parent department.	Number	Yes	Uniquely identifies the parent department to build the hierarchy.
`Managers/string`	ID of the department manager.	Number	Yes	Sets the department manager, used for access control and onboarding/offboarding notifications.
`DateFrom`	Date the department is valid from.	Date	No	Used to activate/deactivate departments.
`DateTo`	Date the department is valid to.	Date	No	Used to activate/deactivate departments.
`LastUpdate`	Date the department was last updated.	Date	No	Used to activate/deactivate departments.
`Status`	Status of the department (e.g., 'A' for Active).	Text	No	Used to activate/deactivate departments.