Try our conversational search powered by Generative AI!

AI OnAI Off

Moving a category to a different catalog in Commerce Manager does work correctly for subcategories and contents of subcategories.

Found in

EPiServer.Commerce.Core 8.15.0

Created

Jul 30, 2015

Updated

Aug 21, 2015

Area

Falcon/Commerce

State

Closed, Fixed and Tested

Steps to reproduce

Steps to reproduce

  1. Using the Commerce Starter Kit sample site, go to Commerce Manager and create a second catalog called "Second Catalog".
  2. Go back to the first catalog "Departmental Catalog" and select a category that contains one or more nested categories. I chose "Departmental Catalog > Departments > Automotive". This contains subcategories like Accessories, Performance, ReplacementParts, and Tools.
  3. Clone the "Automotive" category for the purposes of moving. This operation should take a while since the category is sizeable.
  4. Move the cloned "Automotive" category to the second catalog.
  5. Examine the moved "Automotive" category.
Expected:

In the moved category, the subcategories and nested contents should be visible.

Actual:


In the moved category, the subcategories and nested contents are not visible.

Notes:

Only products and skus immediately under the moved category are visible.
For products and skus in subcategories under the "Automotive" category, we noticed that the [CatalogId] had not been updated properly for records in the [CatalogEntry] table.
For subcategories under the "Automotive" category, we noticed that the [CatalogId] had not been updated properly for records in the [CatalogNode] table whose [ParentNodeId] field referred to the id of the "Automotive" catalog node.
Deleting the moved category from Commerce Manager can have the effect of orphaning the subcategories and nested contents whose [CatalogId] field were not properly updated.
If you move the moved "Automotive" category from the new Catalog back to the original Catalog, all of the nested subcategories and content becomes visible again.