Why did a row in the import file fail, and how do I find out the reason?
After you click Import, the Result page appears. It shows the number of rows in each state, and a message for each row that failed to import, explaining the error reason and the line number:
| Counter | Meaning |
|---|---|
| Imported successfully | New employees created from the file. |
| Updated successfully | Existing employees whose details were updated. |
| Failed | Rows that were not imported because of an error in their data. |
Error messages appear above the counters, and each message states the error reason and the line number in the file, for example: an invalid value for the Type field in line #2. The header row in the file counts as line 1, so line #2 is the first employee row in the file.
Common reasons a row fails:
- A required field is left empty. Required fields are marked with * in the Fields Mapping step.
- A value isn’t accepted, such as a value in the Type column other than user or employee, or an invalid email address.
- A branch, direct manager, or role that doesn’t exist in the system.
- A date in a format different from the system’s date format.
- A code, Official ID, or email address repeated in the file, or an Official ID or email address that belongs to another employee.
🛈
Notes:
- If you turn on Ignore errors while importing in the Fields Mapping step, the system imports the valid rows and skips the rows with errors, and a message appears for each skipped row.
- If you don’t turn on this option, the import stops at the first row with an error, and only that row’s message appears.
- The message shows only the first error in the row. If the row has more than one error, a new message may appear for the same row after you fix the first error and import again.
⚠
Warning: After you fix the failed rows, import only these rows again. If you import the whole file again, the rows that succeeded before with an empty code column will create new employees again.