Summary
When you import users in Integrations, the review screen shows how each row in your file was handled and flags the rows that need attention. This article walks you through reading the import job results, understanding the conflict and error columns, and downloading the affected rows so you can correct and re-import them. The goal is to fix conflicting or failed rows before you treat the import as complete.
Introduction
User imports in Integrations turn a prepared file into a batch of account creations and updates. After a job runs, not every row always succeeds: some rows conflict with existing accounts, and some fail because their data cannot be processed. The import review screen exists to surface exactly which rows those are.
This screen is used by administrators who onboard learners in bulk or keep KnowledgeCity aligned with a roster maintained elsewhere. Instead of guessing what happened, you get a per-job breakdown of created, updated, and failed rows, with the failed rows explained and available for download so you can repair them and run the import again.
Key Concepts
- Import job: a single run of a user import. Each job is listed with its file name, who ran it, the import date, and the total rows in the file.
- Row statuses: every row resolves to one of the outcome columns, Created for new accounts, Updated for existing accounts that were modified, and Failed for rows that could not be processed.
- Match-by field: the identifier (such as Email, Employee ID, or Username) that decides whether a row matches an existing account. It is what separates an update from a new record and is the usual source of conflicts.
- Add, update, and skip actions: the import behavior you chose determines how each row is treated, whether new users are added, existing users are updated, or a mapped column is skipped and left out of the import.
- Failed rows and error descriptions: rows the system could not process. Cells containing mistakes are highlighted in red, and the last column carries a description of the error(s) for that row.
- Downloadable rows: each outcome column offers a report you can download, an Excel list of created profiles, an Excel list of updated profiles, and an error report for the failed rows.
Steps to Follow
Open the Import Job List
You start from the import area, which opens on a list of all previous import processes. Each entry represents one import job and shows its key details: the File Name that was uploaded, the Imported By administrator, the Import Date, and the Rows in File count. Use this list to locate the job you just ran or an earlier job you need to review.
Read the Outcome Columns
For the job you are reviewing, look at the outcome columns that summarize what happened to each row. Created shows the count of new accounts that were successfully added. Updated shows the count of existing accounts that were successfully modified. Failed shows the number of rows that could not be processed. Together these tell you at a glance how much of your file went through cleanly and how much still needs work.
Identify Conflicting and Failed Rows
Rows that did not land as new Created accounts are the ones to focus on. A row is treated as an update rather than a new account when it matches an existing user on the match-by field you selected, so review your Match user by field choice (Email, Employee ID, or Username) if rows resolved differently than you expected. Rows in the Failed count are those the system rejected outright and are the priority for correction.
Download the Affected Rows
To see the detail behind each count, download the report attached to that column. Use the download option on Created and Updated to get an Excel list of the profiles in each group, and use the download option on Failed to get the error report. The error report is the working copy you will correct, because it isolates exactly the rows that did not go through.
Read the Error Details
Open the downloaded error report and look for the cells highlighted in red, which mark the specific values that caused a problem. Read the last column, which contains a description of the error(s) for that row. Common issues include a missing required field or an identifier that does not resolve cleanly against existing accounts. Use these descriptions to understand what to change in each flagged row.
Correct and Re-Import
Fix the highlighted values in your corrected file so each row has valid, consistent data, paying particular attention to the match-by field so add and update actions resolve the way you intend. Then run the import again with the corrected rows. Confirm the results by checking that the previously failed rows now appear under Created or Updated, and spot-check a few records against your source before treating the import as complete.
Conclusion
The import review screen in Integrations gives you a clear, per-job account of which rows were created, updated, or failed, and lets you download the exact rows behind each outcome. By reading the error descriptions, correcting the flagged values, and re-importing, you resolve conflicts and errors so your user records land accurately and stay in sync with your source.