Duplicate of Guide to Unit4 Agresso Data Import

This document provides a detailed description of the fields in the XML master data file imported from Unit4 Agresso. It is intended for technical staff 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.

XML

<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	Required	Usage
`Address/Street`	Street address.	String	No	Not used.
`Address/Location`	City or town.	String	No	Not used.
`Address/Zip Code`	Zip code.	Integer	No	Not used.
`Address/Mobile`	Mobile phone number.	Integer	No	Used in notification workflows for onboarding and offboarding.
`Address/EmailList/string`	Email address.	String	No	Used in notification workflows for onboarding and offboarding.
`jobs/job@resourceID`	Employee number.	Integer	Yes	Uniquely identifies the employee within the company.
`jobs/job/jobType`	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.
`jobs/job/MainPosition`	Indicates whether this is the employee's primary position (`true`/`false`).	String	No	Used for messaging, user account management, and access control.
`employment/employment/Percentage`	Position percentage (e.g., 100).	Integer	No	Used for messaging, user account management, and access control.
`jobs/job/PostId`	Position Code ID.	Integer	No	Used for messaging, user account management, and access control.
`jobs/job/PostIdDescription`	Job title.	String	No	Used for messaging, user account management, and access control.
`jobs/job/Postal Code`	Position code.	String	No	Used for messaging, user account management, and access control.
`jobs/job/PostalCodeDescription`	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/area of responsibility.	String	No	Used to indicate which department and role the user belongs to.
`jobs/job/DateFrom`	Start date for the specific position.	Date	No	Used for access control and to enable or disable user accounts.
`jobs/job/DateTo`	End date for the specific position.	Date	No	Used for access control and to enable or disable user accounts.
`DateFrom`	Start date of the entire employment relationship.	Date	Yes	Used for access control and to enable or disable user accounts.
`DateTo`	End date for the entire employment relationship.	Date	No	Used for access control and to enable or disable user accounts.
`First Name`	First name.	String	Yes	Used in notification flows.
`Last name`	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.
`Social Security Number`	Norwegian National ID 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 to `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 section 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.

XML

<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	Required	Usage
`Company Code`	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`	The department manager's ID.	Number	Yes	Sets the department manager, used for access control and onboarding/offboarding notifications.
`DateFrom`	The date the department becomes effective.	Date	No	Used to enable or disable departments.
`DateTo`	Date until which the department is valid.	Date	No	Used to enable or disable departments.
`Last Updated`	Date the department was last updated.	Date	No	Used to enable or disable departments.
`Status`	Status of the department (e.g., 'A' for Active).	Text	No	Used to enable or disable departments.