We have a reasonably large catalog running on Commerce 9.6 with 37 000 SKU's mapped into products making up a total 56 434 CatalogEntries. The catalog is completely maintained with InRiver PIM, which means that the metadata is also created by the InRiver connector.
Initially we had not configured the InRiver connector properly, which meant that a LOT of unnecessary metafields were pushed into the catalog. This was not an issue before but now the catalog has grown in size to a point where I feel were seeing performance degradation because of the "garbage" metadata. The rowcount of CatalogContentProperty for custom MetaFields mapped to CatalogEntries is 2219264 which averages to about 39 MetaFields per CatalogEntry, when the optimal count would around 25 MetaFields.
In this thread there's instructions on how to unlink MetaFields from MetaClasses after which the MetaFields can be deleted completely:
https://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=142928
The problem I'm having, is that I could only unlink four newest MetaFields successfully. After this, when I do these steps:
Go to the Commerce Manager Administration section => Catalog => MetaClass => Select the type of class (Node or Entry), then select the MetaClass you would like to edit. Then uncheck the properties you don't want to be in the MetaClass, then click OK to save.
I get the "Changes have been successfully saved." notification BUT the link is not removed and the corresponding checkbox remains checked. This obviously means that I can't delete the MetaFields as the links between MetaClasses are not removed.
The MetaClasses and most of the MetaFields were created in Commerce 7.5 in 2015 and our environment has since been reguraly updated to version 9.6 where we are currently.
Is this a glitch in our version of Commerce Manager or is our database possibly corrupt?