Product Resources

⇦ BACK TO GUIDELINES AND RESOURCES

Five things you need to know to create perfect and future-proof import files to use with the new import wizard. Each of the items is further detailed in the Expert overview for import UI v2.

Import file checklist

2023.04 and older	2023.05 onwards
1 – Community, domain and domain type (see A)
You must explicitly provide and map the community, domain and domain type.	It is recommended to provide and map the community, domain and domain type explicitly. If the domain is not mapped, it defaults to the current domain.
2 – Asset type (see B, C)
You must explicitly provide and map the asset type.	You must explicitly provide and map the asset type. – Update: 2023.08 onwards, while explicit mapping is still recommended, the asset type will be defaulted when not mapped for most comon use cases. (planned - see B)
3 – Partial data (see D)
All the mapped columns (Asset Type, Community, Domain and Domain Type) must contain valid values in the input file. If some rows have missing values, they are not auto-defaulted.	No changes
4 – Unwanted spaces (see E)
You must remove all the unwanted leading or trailing spaces contained in the input file.	No changes
5 – Automapping of relations (see Improvements)
Identical to Import UI v1	A more detailed relation header format (Asset Type relation Asset Type) improves relation mapping. The old header format remains supported.

QUICK LINKS
BACK TO GUIDELINES AND RESOURCES | PRODUCT DOCUMENTATION