1

We are using Sitecore commerce 9.2 and facing an issue while assigning an imported catalog from another environment to a new storefront site. Though the catalog is not associated with any other site in the current environment but still the Sitecore system throwing the below error:

'<CatalogName>' is already associated to another site

Below is the screenshot of the error message:

enter image description here Please help to resolve the issue.

Improve this question
3
  • can you check on /sitecore/Commerce/Catalog Management/Catalogs if the catalog is selected here ? – Vlad Iobagiu Feb 12 '20 at 7:54
  • I checked on /sitecore/Commerce/Catalog Management/Catalogs path and found that the catalog is not selected. But while trying to select the same and click on save it is throwing the same error as mentioned above. – Dipra Dutta IN Feb 12 '20 at 8:00
  • You mentioned multiple environments in your question. What do you mean with the environments? Does that mean the catalog is associated with a site? – James Feb 27 '20 at 13:20
0

I was given the following solution by a work colleague.

  1. open the catalog (zip file) that was imported via PostMan (you may need to use 7Zip to do this as Windows explorer might complain about it being a readonly file)
  2. open Catalog.1.json
  3. find all instances of the property "ParentCatalogList" and clear the associated Guid value (so you have "ParentCatalogList":"")
  4. save Catalog.1.json back into the zip
  5. re-import the zip into Commerce using PostMan
  6. you should now be able to select the catalog within Sitecore
Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.