HR Import 2.0 is the updated version of the existing HR import functionality (HR Import 1.0). It’s different from HR Import 1.0 as follows:
- Uses the HR API framework to run validations and write data to the database.
- Updates one employee record at a time instead of performing bulk updates, which allows for better error handling and improved background job performance.
- Requires fewer fields to update an existing employee. First name, last name, and employee number are optional in the import file for HR Import 2.0.
Other benefits of the HR Import 2.0 include:
- Support for Position Management. For example, you can use the import to mass assign employees to vacant positions.
- Enhanced data mapping functionality. The legacy data mapping process applies the suggested values based on the current date, regardless of the effective date of the qualifying data. Data Mapping 2.0 applies suggested values based on the effective date of the qualifying data.
The process of running the HR import hasn’t changed and HR Import 2.0 functionality is backward compatible with HR Import 1.0 functionality, using the same import XSD schema and directory path. As a result, you can use the existing import file without making any changes to it and you can send the file using the same directory path that you use with HR Import 1.0. In some cases, however, tokens may no longer be fully supported because a different token replaces it. For example, Job and Org are replaced by WorkAssignment. See the Dayforce HR Import Interface Specification document for more information.
HR Import 2.0 can be configured with data mapping rules, just like HR Import 1.0. Data mapping rules define what assignments are automatically made during the import. See “Employee Data Mapping Rules Setup” in the HR Administration Guide.