Errors By Import Stage

Errors are handled differently during different stages of the import.

  • Upload: The data is first loaded from files into data source tables. The loading may fail if the data in the file cannot be loaded. In this case, the errors are reported in an error file for the load step.
  • Import: The import step can generate various data validation errors, such as:
    • Data does not match the target attribute format and cannot be converted correctly. This can happen if the data type of the data source attribute or expression is different for the data type of the repository attribute it is mapped to. In this case, the whole record is rejected.
    • Data truncation warning - some data was truncated to fit the target attribute size.
    • Rulebase data validation error if a rulebase was specified.
  • Validate: The records rejected by the rulebase validation are moved into a separate record collection.
  • Manage Record collection: When records cannot be bundled correctly. Bundling is needed only if you import hierarchical data and if you need to spawn a workflow for each hierarchy. If the same children are part of multiple hierarchies, the bundling will fail. In this case, you need to import in multiple passes.
  • Rejection: If a row is mapped to more than one repository, import may reject one of the mapped records. During rejection, the parts of the rows mapped to other repositories are not rejected.