Order of Processing
  • 10 Jan 2024
  • 1 Minute to read
  • Dark
    Light

Order of Processing

  • Dark
    Light

Article Summary

The table below lists all the sections available by default together with and their corresponding datasets in the recommended order of processing, as some datasets use the information from other datasets. For example, the Job Positions dataset comes after the Organizational Units dataset, since it uses information about the organizational units. At the same time, this order is not mandatory (for example, the Job Roles dataset does not depend on Organizational Units, therefore, the order is not important in this case).

The Key Field(s) column specifies the key field(s) for each standard dataset. When data is being imported, Lanteria HR uses the key field(s) to identify whether a record is new.

Section

Dataset

Key Field(s)

Dictionaries

Currencies

Code

Countries

Title

Locations

Title

Companies

Title

Cost Centers

Title

Legal Entities

Title

Organizational Unit Types

Title

Employment Types

Title

Organizational Units

Organizational Units

Title

Organizational Unit Manager and
Parent Organizational Unit

Title

Job Details

Job Grades

Title

Job Categories

Title

Job Roles

Title

Job Positions

Code

Job Requirements

Title, Job Role

Job Responsibilities

Title, Job Role

Employees

Employees

By default, Title and Employee Global ID are used as key fields. To set up Title
and AD Account to be used, set the Use AD Account as a key
for employee data import
to yes (this setting is available only from the General 
Settings list - click Settings > Site Lists and Libraries > General Settings).

Salary Details

Employee

Employee Sensitive Data

Employee

Competencies

Competency Levels

Score

Competency Areas

Title

Competency Groups

Title

Competencies

Title, Competency Group

Competency Level Descriptions

Competency, Level, Job Role

Job Role Competencies

Competency, Job Role

Competency Criteria Types

Title

Competency Criteria

Title, Competency

Historical Data

Employment History

Employee, Start Date, Org Unit, Job Position/Job Role

If JobAssignmentMode = JobPosition, Job Position is used; 
otherwise, Job Role is used

Salary History

Employee, Effective Date

Each dataset is essentially a SharePoint list, which you can edit by clicking Actions > Edit in Datasheet View.


Was this article helpful?