Failing Widget: 'SC Catalog Item'

ericgilmore · ‎09-13-2019

Just loaded an update set from our dev instance to test, with 3 new catalog items. For two of the items I get this when I try to access them from the portal:

The third catalog item is using the SC Catalog Item widget just fine. What gives here?

ericgilmore · ‎09-27-2019

Here's what I managed to suss out. After examining the variables contained within the catalog item, I found that 2 were essentially pointing to places that hadn't be translated over by the update set. One was a List Collector that was pointing to a non-existent List Table (Type Specifications tab), the second was a Macro that was pointing to a non-existent Widget (Default Value tab).

After manually pulling this data over via exported XML files, things came around. I'm 95% sure this was it, although I didn't confirm (via logs) that these were the explicit things which caused the errors to be thrown.

View solution in original post

Daniel Hope · ‎12-15-2022

This was the exact issue I had. Had 2 variable I cleared the "field" value for but "Map to field" was not set to false

Sree21 · ‎06-14-2023

Experienced the same issue as in the posted question. Found out the cause was record producer variables which were mapped to table fields and those table fields did not exist in Prod. Tested by deactivating those variables and the error was gone.

Oleg · ‎09-14-2019

The information, which you posted is't full enough to help you. The console log of web browser contains the code fragment, which throws NullPointer exception. It could be some problem on Catalog Script or some problem with multi-value variable, but I'm afraid nobody could help you without seen information from console log and without additional information about the corresponding catalog item.

ericgilmore · ‎09-14-2019

Ok, here's what I'm seeing when I click on the catalog item link in the portal;

I don't think it's very helpful, but maybe I'm completely missing something.

Community Alums · ‎09-24-2019

This looks troublesome to me.

However, there still appears to be not enough information provided to diagnose the issue.

Can you provide more error logs ?