HR Import 2.0: Error Messages

HR Import 2.0 and Data Mapping 2.0 Guide

Version
R2025.1.1
HR Import 2.0: Error Messages

Before You Begin: You must have the Can Download Error Files role feature enabled for your user role to access the Error File subtab described in this topic. See “Assign Role Features” in the Dayforce Implementation Guide.

You can access the error messages in the import's job log in the Debug Information subtab and the Error File subtab of the Jobs Log tab in System Admin > Background Jobs:

  • Debug Information: This subtab is also used by HR Import 1.0. It displays a high-level overview of the errors encountered during the HR Import, including the employee number affected and the entity and field that caused the error.
  • Error File: This subtab is for HR Import 2.0 only. It contains a link to download an XML file that contains further details about the import errors. When HR Import 2.0 doesn't update records due to validation errors, it creates a downloadable HR Import XML file that lists these employee records. Commented on top of each employee record are the validation errors detected. Users can download the file, fix the problems, and then re-import the failed employee records without having to re-import the original, larger, file.

Improved Error Handling

HR Import 2.0 can reduce the amount of time it takes to troubleshoot import failures as follows:

  • Instead of the entire import failing when the information for a few employees is wrong, the application saves the records of the employees from the import file that passed validation.
  • Within the import background job log's debug file, HR Import 2.0 consolidates validation errors by employee number. As well, validation messages indicate which entity and value caused each error. Both of these improvements can help users identify and address the problems.

Example

HR Import 2.0 error messages are organized by employee number and list the specific entities and fields that caused each error. For example, the following error information in the Debug Information subtab identifies which entity (EmploymentStatus, Role), record (2021-10-01), and field (PayType, RoleXRefCode) caused the error:

  • Employee Number: G00086
  • "Failed to Save Employee Data"
  • "EmploymentStatus 2021-10-01 PayType[Hourly] Value provided in file is not valid"
  • "Role 2021-10-01 RoleXrefCode[CAssociate] Value provided in file is not valid"

The following screenshot shows what these HR Import errors look like in the Debug Information subtab:

Debug Information sub-tab showing sample import errors.

The following screenshot shows what these HR Import errors look like in the XML file, opened from the Error File subtab:

XML file import error sample.