dependentelement
dependentelement
Determines how dependencies of the specified item type are handled. For example, a product has a set of associated attributes. During an import operation, the product being imported may have a different set of associated attributes than the product in the destination system. This setting specifies whether the existing attributes on the product are removed and replaced with the imported attributes, or if the new attributes are added to the existing set of attributes.
If the import configuration does not contain a dependentelement for a particular item type, then the default behavior for dependencies of that item type is CLEAR_COLLECTION.
Supported values are:
- CLEAR_COLLECTION: Remove all existing dependencies of this type before adding new dependencies from the import package.
- RETAIN_COLLECTION: Keep existing dependencies of this type and add only new dependencies from the import package, if any.
The payment_methods collection element only supports the CLEAR_COLLECTION value. If any other value is used, the Import-Export tool will return an exception.
Attributes
Name | Number of occurrences | Description |
---|---|---|
type | 1 | Specifies the type of dependency. For categories (CATEGORY), possible values are:
For products (PRODUCT), possible values are:
For system configuration settings (SYSTEMCONFIGURATION), possible values are:
For price lists (PRICELISTDESCRIPTOR), possible values are:
For payment gateways (PAYMENTGATEWAY), possible values are:
For user roles (USER_ROLE), possible values are:
For coupon sets (COUPONSET), possible values are:
For CM import jobs (CM_IMPORT_JOB), possible values are:
|