Import Errors

Importing data looks very appealing although the data should match the structures in the tool. Mismatches in structures will cause import errors, regularly a source of frustration.

As an example, we create deliberate import errors during training sessions to illustrate the effect and guide users to follow up on the errors:

This picture shows the effect of non-existing location types in an import, and the effect on the import wizard.

It is emphasizes that data accuracy is important and small differences will block the import.
There are a few options provided to export the import file showing the errors, where it is recommended to actually 'enter' the faulty marked data lines - by hand in the IMS User-Interface - where the most obvious errors wil become clear, for instance where hierarchy data or common data does not match.

For clarity:

• The import wizard will not create new objects like for instance new Task Names, Failure modes and Frequencies. Neither: Location types, Equipment groups, CMMS types, Plants nor Units.
• The import wizard will not enter 'the good data' and leave out 'the bad data' of a particualr import action. To avoid uncertainty on the loaded content, the whole importfile is rejected. It is up to the user to decide to split up the import file and just import a part - without errors.

However, there can be a wide variety of data issues with virtually infinite possibilities of what can be wrong, where the import wizard may on be limited in feedback what the actual problem is.
Typical recommendation involve:

• Avoid a first 'export + import' of >5 k lines, just start with 5 lines and check your result. Where the import can update data very quickly, it will also in case the update appears to be wrong. Working wil a small dataset and checking the result - before moving to bigger files helps ensure quality end result.
• Massive imports (> 20k lines) are discouraged as the updates may take long in the background to finalize and user may 'react' on a partially completed import.
• In case of unexpected or unclear errors, try to create a 'copy data set' in - for instance - the acceptance database with 'clean data', to see where the imports work well and where they do not.
  As an example: During trainings sessions many mistakes can be made by the students - by incident - sometimes leading to unexpected situations and unexpected import errors. This illustrates a situation where most of the class completed the import exercise sucessfuly, others mat be looking at errors they don't understand - as they might be unaware of inconsistencies that were created in the first place.
• When creating a support ticket, explain and document clearly what the issue is, what the error messages are and what was expected.

Finally: note there is an import log as part of Settings/Data Transfer/ Import History, for succesful imports done.
{height="" width=""}
This log enables to download the import file later.