TB.One > Import & Export > Master Data Import via TB.Cat/XML > Options for Field Assignment

Options for Field Assignment

There are several ways of adding properties such as components, attributes, brands and service logos to existing entries. There is a distinction between name (or designation) and key-based assignments.

 

ATTENTION:
It is possible to combine both types of assignments (name and key-based), e.g. name-based referencing for components and key-based referencing for attributes. However, it is not possible to change the assignment base within one node (e.g. referencing the component "color" name-based and the component "material" key-based).

NAME

You can submit the names of properties directly in the product. Keep in mind that all properties must have a unique name.

<P_COMPONENT identifier="name" key="Length">

<VALUE xml:lang="x-default">110cm</VALUE>

</P_COMPONENT>

In the import settings it is possible to configure that any new properties are created in TB.One during the import process.

You should only choose name-based import if you do not have keys for the properties at your disposal.

KEY

Key-based imports are recommended over name-based imports, because the reference will not be lost even if the property name is changed. Additionally, it is possible to control the number of imported properties (e.g. only import if a corresponding key is stored in TB.One).

In TB.One, you can define one key per property, which is then used for the assignment during the import. You can configure the import settings, so that the import keys of all new clusters, brands, components, attributes, service logos, IntraStat numbers and countries of origin are automatically created during import.

<P_COMPONENT identifier="key" key="wid">

<VALUE xml:lang="x-default">110cm</VALUE>

<VALUE xml:lang="en-us">43.31 in</VALUE>

</P_COMPONENT>

 

Tradebyte recommends key-based data referencing for imports. If you choose to create new properties via import, the key will also be used as the name/designation, unless you transfer a separate name in addition to the key (see example below). In that case, both the key and name are taken over. If you only refer to properties that already exist in TB.One, indicating the name is not necessary.

<P_COMPONENT identifier="key" key="wid" name="Width">

<VALUE xml:lang="x-default">110cm</VALUE>

<VALUE xml:lang="en-us">43.31 in</VALUE>

</P_COMPONENT>

For further information, see also:

•Master data import via XML - overview