How to troubleshoot user import errors

If an HR data import fails for certain users, you can find details about the cause in the import log. This guide explains how to locate and interpret these error messages to resolve import issues.

Users who fail to import due to data errors are highlighted in the import history.

Step-by-step guide

1. Go to Synchronization > Import history.

2. Click on the most recent import job to view its details. Look for the "New accounts that failed" field.

3. Click the filter icon next to "New accounts that failed" to view only the log entries related to those errors.

   4. Select the Import Log tab to view the specific error messages.

4. Read the error message to determine the cause.

   • Note: In the example below, the error message indicates that a date value is outside the acceptable range (e.g., before January 1, 1753, or after December 31, 9999). This is often caused by a typo in the source HR system.

   6. Identify the affected user. The error message often includes a unique identifier, such as an employee number (employee number), in parentheses. Make a note of this number.

5. Download the original import file and search for the employee number to locate the user's complete data record. This will allow you to verify the incorrect data.

   XML
   

   <company>
       <companyId>1</companyId>
       <companyName>...</companyName>
       <organizationNumber>...</organizationNumber>
   </company>
   <employeeId>9999</employeeId>
   <employmentPercentage>0.0</employmentPercentage>
   <lastChangedDate>2023-04-13T12:35:39</lastChangedDate>
   <lastDayOfEmployment>0203-05-01</lastDayOfEmployment>
   

6. Contact the HR department (or the administrator of the source system) with the employee number and the incorrect data. They must correct the information in the source system before the next import can succeed.