Choices are visible in the portal and but showing up in the try it option for the same catalog item

NisargaK
Tera Contributor

Hi @Everyone, 

 

 

I have a scenario where we have categories and subcategories for a catalog item. These both categories and subcategories are stored in a custom choice table. The issue here is that when we select the category in portal, we are able to select subcategories that are dependent on the selected category.

 

But when we try the same in the catalog item’s try it option, we can select a category, but the subcategories field is showing none. We have checked reference qualifiers and other things; everything seems good to me.

 

The UI scripts and client scripts were updated a few years back, not recently, but this issue happened recently. Any idea on this? Can someone please suggest something on this?

5 REPLIES 5

saibharath8
Tera Contributor

This looks like a UI rendering difference between Service Portal and the native “Try It” view. Portal supports Angular/UI scripts, but the native catalog form only supports standard client scripts using g_form.

If the subcategory population logic depends on Portal-specific scripts or old UI scripts, it won’t execute in Try It, which is why the field shows empty.

I’d suggest checking the client script UI type (set to All), avoiding Portal APIs, and using a GlideAjax-based onChange script to populate subcategories. That approach works consistently in both Portal and Native UI.