Skip to main content
Skip table of contents

Staging | SDZeCOM Staging

The fields do not provide any setting options.

However, they can be read using a formula, e.g. with ATTRVAL. Hover over the field to find out the ID of the field (negative number!) and insert it into your formula.

In a second step, you can use the SDZeCOM Rules+ to write back the result of this formula into another attribute and make the information searchable.

Field

Description

Linked PIM product

This field is filled automatically after a Staging object has been copied to a PIM object for the first time.

The label and ID of the PIM product are displayed here.

PIM search value

This field is relevant if a product is first created in PIM and returned to the ERP from there. The article is later returned to Staging via the ERP import and is then recognized with the help of this attribute.

PIM search field

Select the standard attribute in PIM to be searched for the matching PIM counterpart to the Staging object.

Ensure that the value is always contained in the XML and is unique in PIM.

Usually, the external key is chosen.

PIM search attribute

If you do not want to use a standard attribute for searching for the matching PIM object (see above), you can alternatively select a customer-specific, searchable PIM attribute here.

Select the standard attribute in PIM to be searched for the matching PIM counterpart to the Staging object.

Usually, the external key is chosen.

Alternative external key field

If the external key is not recognizable in the XML or another attribute is supposed to be used as the external key, select the appropriate attribute. You can also use a formula attribute.

Alternative label field

If you do not want to use the XML field that was identified as the external key and label for the label, you can select an alternative attribute as the label.

Temp folder

Select a PIM folder (e.g. INBOX) in which objects are created when their parent cannot be determined, and which therefore cannot be categorized in the product tree.

PIM parent search value

Select the attribute in the XML of the Staging object that contains the information on the matching parent element in PIM.

If there is no unique attribute in the XML, you can create a formula attribute.

PIM parent search field

Select the standard attribute in PIM to be searched for the matching PIM parent element for the Staging object.

Select the standard attribute in PIM to be searched for the matching PIM counterpart to the Staging object.

PIM parent search attribute

If you do not want to use a standard attribute for searching for the matching PIM parent element (see above), you can alternatively select a customer-specific, searchable PIM attribute here.

Select the standard attribute in PIM to be searched for the matching PIM counterpart to the Staging object.

Usually, the external key is chosen.

Don’t set external key

Activate this option to prevent the external key of the PIM object from being overwritten by that of the Staging object.

This is useful, for example, if you create objects in PIM and only want to update them by Staging.

Don’t create new products

You can use this option to prevent new objects from being created in PIM by Staging.

Don’t set label

Decide whether the label from the import is to be written to the PIM object or not.

Create as folder

This attribute controls the system attribute “Folder". Specify whether the imported objects are endpoints or folders.

Don’t move outside temp folder

Decide whether the PIM product found is to be moved outside the PIM temp folder (e.g. the INBOX).

If the option is deactivated, the object is moved inside and outside the temp folder each time it is updated according to the data determined for the parent search. See above: PIM parent search value, PIM parent search field, PIM parent search attribute

If the option is activated, the object is always moved within the temp folder, but only once outside it. As soon as it is outside the temp folder, it is only updated but no longer moved.

Consequently, if no parent could be identified when an object was created, the product is stored in the INBOX, for example. From there, you assign it manually to the correct parent node. During the next update, the system recognizes that the object was moved manually and only updates it.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.