CSV and TXT imports through the Ataccama RDM Web UI can complete with non-intuitive status messages, making it difficult to understand what happened or how to fix the input file.
This article explains the most common import messages, what they mean, and where to find additional information to diagnose and resolve import issues.
Import Completed Successfully
Two common scenarios produce the same completion message.
| Scenario | Message | Meaning |
| Records were created or updated | ‘Import’ operation finished successfully. | The import completed and changes were applied. |
| Imported data is identical to existing records | ‘Import’ operation finished successfully. | The import completed successfully, but no changes were required because the imported data already matches the current data. |
Import Completed with Warnings
A warning indicates that the import completed, but some records could not be processed.
| Scenario | Message | What happened |
| Parsing errors or missing columns | Import operation finished with warnings. Look at System → Action History. | Records that could be processed successfully were imported. Records affected by parsing errors or schema mismatches were skipped. Review Action History for details. |
When warnings occur, open System → Action History to review the detailed validation or parsing errors for individual records.
Import Failed
A failed import means that the import process could not complete.
Common import errors
| Cause | Message | Resolution |
| The CSV header does not match the target dataset attributes. | No column in the header matches any column in the imported table... | Verify the column names, spelling, case, and underscores, ensure the correct dataset is selected, and review the import settings. |
| The CSV file is incomplete or malformed. | UNEXPECTED_EOF | Verify that the CSV file is complete and properly terminated. Use an editor such as Notepad++ to display end-of-line characters and check for missing line breaks, unclosed quoted fields, or a missing final line terminator..  
|
Note: For large files, the import may first display the message:
Operation 'Import' sent to background. Look at the System menu.
See Background Import
This only indicates that the import has started as a background operation. The final result is available in System → Long Operations (while the import is running) or System → Action History (after completion). If the import fails, the actual error (for example, UNEXPECTED_EOF) is reported there.
Background Import
For larger files, the import is started as a background operation.
Background Import is not a final status. It only indicates that the import continues asynchronously.
| Meaning | Message | Monitor |
| The import continues in the background. | Operation 'Import' sent to background. Look at the System menu. | System → Long Operations |
Troubleshooting Tips
Before importing, verify the following:
- the correct dataset is selected;
- the CSV header matches the RDM attribute technical names;
- the file encoding and delimiter are correct;
- the CSV file is complete and not truncated.
Whenever an import finishes with warnings or fails, review System → Action History to identify the affected records and the underlying cause.
Import messages describe the overall outcome of the operation, but they do not always indicate whether records were created, updated, skipped, or left unchanged.
For successful imports, it is important to distinguish between data that was actually loaded and data that already matched existing records. For imports completed with warnings or failures, System → Action History provides the detailed information required to identify and resolve the underlying issue.