Staging | Special features / deviations of standard fields
Field | Description |
Attribute type |
The attribute type in Staging must correspond to the attribute type in PIM to which it is copied. For selection fields or numbers with units of measurement, also select the corresponding value lists or units of measurement in Staging. However, this does not apply to filling from tables. As regards valuerange attributes in PIM, we recommend creating them as valuerange attributes when importing them into Staging and setting the correct values via XSL transformation. Alternatively, it is possible to write the value of a text attribute to a selection attribute using SDZeCOM Rules+ “Write back result” and set the values this way. |
| These fields are taken from the XML file and originate from the source system. |
| These fields correspond to those in the other studios. You can name them as in the PIM, but also completely independently. It is conceivable, for example, that individual tabs are assigned to individual imports and then combined into a golden record in the object. You can also display attributes that are copied to PIM in another section than the attributes that are not copied to PIM. |
In table attributes
Field | Description |
Xpath for Row Key | Specify an X path to compose a unique external key for the table rows. This ensures that existing table rows are updated when they are transferred again. Example 1
Example 2
The Xpath must be specified in order to be able to use the two functions described below. This procedure prevents existing or edited/added table rows from being overwritten with each reimport. |
Don't clean on Integration import | Activate this option to prevent table rows from being cleaned up. |
Don't delete on Integration import | Activate this option to prevent table rows from being deleted. |