Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Dependency Conflicts

Dependency Conflicts

In addition to specifying conflict resolution, you can configure how to handle dependencies of those objects when there are conflicts. A dependency conflict occurs when an object exists in both the import package and the target system and each version has different dependencies.

There are two options for handling dependency conflicts:

  • Clear collection. This option removes all existing dependencies of the specified type from the target object and adds any new dependencies.
  • Retain collection. This option keeps existing dependencies and adds any new dependencies to the target object. If the import package contains updates to existing dependencies the updates are applied. (Note that this option is not available for Product Bundles. Product Bundles must use Clear collection. This ensures that the ordering of bundle constituents is maintained.)

For example, an Elastic Path deployment contains product X, which has product attributes A, B, C, D, and E. The package being imported contains product X as well, but has a slightly different set of product attributes; it does not have A and it has a new product attribute, F.

If the Clear collection option is selected, the existing dependencies are removed. The net effect of this is that product attribute A is removed, F is added, and any changes made to the other product attributes are applied.


If the Retain collection option is selected, the existing product attributes remain the same and F is added. If the import package contains updates to existing product attributes, the updates are applied.