Forum Discussion
Issues with SharePoint Product Catalog (Classic)
Is it a known issue for search-based web parts (content search web part or search box, refiners and results) to be interfering with a page layout integrated with catalog item reuse snippets in SharePoint Online (classic)?
Due to the limitation in creating a product catalog site in modern experience, we went down the path of creating a classic version of product catalog in SharePoint Online. For a year and a half, the product catalog has been working fine until recently while there were no new changes made to the page or the page layout. The page used to surface catalog item content based on the product tag in the URL (https://[tenantname].sharepoint.com/sites/products/overview.aspx?myproduct=apple) as well as search-based content.
Upon investigating the issues, it appears that the catalog item reuse snippets on the page layout and the search-based web parts both are interfering with each other's. If we removed search-based web parts from the page, the catalog item content then surfaces. If the search-based web parts are re-added, the catalog item content then disappears. Has anyone experienced this issue?
2 Replies
You’ve confirmed Catalog-Item Reuse content renders until search web parts are added. Microsoft documents that reuse snippets depend on one Catalog-Item Reuse data-provider web part; if its catalog query stops returning an item, dependent fields can be blank.
On a page copy: 1) ensure that provider remains in the Body zone; 2) test its query for an affected URL and confirm its catalog result source; 3) add search web parts individually, checking their result sources; 4) verify the catalog list is searchable, and reindex it only after a schema or property-mapping change; 5) review Custom script, because Microsoft lists these search parts and Catalog-Item Reuse as affected when scripting is blocked. I can’t confirm a documented known issue. Microsoft now states cross-site publishing is unavailable in SharePoint Online, so if this remains, check Service health and open a SharePoint support request with the URL, UTC time, and any correlation ID.
Thank you for the reply, Jamony. I did some checking based on the information you provided and have verified/confirmed a few things. I've tried allowing custom scripting on the site for which doesn't make any difference. Same with reindexing the site. Since I haven't seen any reports of this issue in the service health, I've raised a ticket with Microsoft. The latest response was we cannot assist you due to customization and scripting... I am thinking, if it had been working for a while and we didn't make any changes recently, then what changed on the Microsoft's side?
