Import Excel: Attribute Names

PART OF OCTOBER 2023 UPDATE

If the naming of the attribute names included an underscore, those values were not imported. Therefor a fix has been deployed. This has impact on all current integrations. Below you find the details what is changed.

The construction of the header is as follows:

Attribute_NAMEATTRIBUTE_LANGUAGE_CHARFIELD

The elements are:

Attribute is the fixed prefix.
NAMEATTRIBUTE is the specific unique name of the attribute
LANGUAGE is not mandatory but only in the header if the field is localisable
CHARFIELD is the characteristics of the field/attribute ( for example: TEXT, SELECTONE)

The issue in this header was with the NAMEATTRIBUTE part. An underscore in this part broke up the construction of the different elements of the Attribute. The solution to exclude this part from breaking up the structure, is to put it in Brackets ‘[ ]’.

This means following:

> old construction: Attribute_Description_en_Text

> new construction: Attribute_[Description]_en_Text

In all new exports you can see that the change is now effective. If those exports are used to import new values, you won’t experience any problems.

Although, if there are imports based on old constructed data/excel sheets, it will not import the values of the attributes. You need to revise the header values as explained in the info panel.

Double check your existing files which are used to import data into ORP. All headers of the columns has been changed and needs to be adjusted to the applied new structure as in the info panel. Only then the data will be imported into ORP.

TIP: Export one product with the attributes which needs to be imported/presented in file. Copy the columns and paste those in the structure of the other file.

Example of new import excel:

Example of Import Excel with new header information