Import Errors

Data accuracy is important and small differences in structure often block the import. When importing data, the data should match the structures in the tool.

When importing data, remember:

• The Import Wizard does not create new objects, including new Task Names, Failure modes, Frequencies, Location types, Equipment groups, {{glossary.CMMS}} types, Plants or Units.

• The Import Wizard does not enter 'the good data' and leave out 'the bad data' during a particular import action. To avoid importing incorrect data, the whole import file is rejected. It is up to the user to decide to split up the import file and just import the part without errors.

Best Practices

When importing data in {{glossary.IMS}}, you may encounter various data-related issues. The Import Wizard may provide limited information about the actual cause of an issue. To help identify and resolve problems, consider the following recommendations:

• Avoid importing large amounts of data (more than 5,000 lines) as a starting point. Start with a small dataset (for example, 5 lines) and verify the results before importing larger files. Working with smaller datasets helps ensure data quality and identify potential issues early.

• Avoid performing very large imports (more than 20,000 lines), as processing may take a long time to complete. During this time, users may work with partially imported data.

• If you encounter unclear or unexpected import errors, try importing the data into a separate test dataset (for example, in the acceptance or testing database) that contains only clean and validated data. This helps determine whether the issue is caused by the import process or by inconsistent or incorrect data.

• When creating a support ticket, clearly describe the issue, include any error messages, and explain the expected outcome.

Finally, note that import logs for successful imports are available in Settings > Data Transfer > Import History.