Hierarchy must be defined in headers
Object hierarchy is defined exclusively in the headers, not in the data rows.
Parent–child relationships are derived from the header structure, and the importer does not use row order,
indentation, or naming conventions to determine hierarchy. Each row represents a single instance of the
root object, while child objects are declared through their corresponding headers.
Multiple objects in a single cell
When adding multiple objects in one cell, they must be separated using a newline
(Alt + Enter in Excel). Newlines are treated as structural delimiters and should therefore be avoided
elsewhere in the data. Free-text fields such as descriptions or notes should not contain line breaks
unless they are intended to represent multiple values.
Duplicate object handling
Objects are identified by a combination of Name and Template.
If both are identical, the importer treats them as the same object, even if they appear in different
rows or under different parent objects. Reusing the same name and template will therefore not create
a new object, but reference or update the existing one.
CSV format and Excel export behavior
The Smart Importer accepts CSV files only. When exporting from Excel to CSV,
any formulas are converted to their calculated values, and the formulas themselves are not included
in the file. Ensure all calculated results are correct before exporting, as the imported data will
consist of static values only.
Following these prerequisites ensures predictable imports, correct hierarchy creation,
and consistent object mapping within the Smart Importer.
