How to understand overlap of objects/ontology resources between marketplace product installations?

I have two marketplace products.

  • The first product included Object Type A.
  • The second product included Object Type A (by mistake) and Object Type B.

So when I install my two products, there is some overlap - where Object Type A has been installed twice.

How can easily detect those overlap ? And even clean up the installations (aka delete Object Type A created by the second package)

More broadly, is it possible to understand overlap between:

  • installation and installation ?
  • installation and non-installed product ?
  • product and product ?

Of course, in real world scenario, this can happen with many objects/actions/functions/etc. overlapping.

Hi @VincentF

I witness this first hand, especially when refactoring or splitting large Marketplace products. It would be highly beneficial to have a feature that allows “diff” between different Marketplace products, including those across separate stores. Also, particularly important in scenarios where products are initially developed in isolation and later need to be linked, as teams realize interdependencies across stores. Raise this with the Marketplace team, as there seems to be a need for greater flexibility and enhanced tooling to support these scenarios.