Catalog items difference in backend and client

[dev_K]

hello everyone!

I have a question:

I have a catalog item which correctly displays security zones in a dropdown menu (options depend on selection of other field) when i make a request via ESC: 

however when i do exactly same thing via backend, those options are not populated.

Just FYI, there is a script includes called, that contains the list of options for that fields.

Any ideas why that is happening?

[dev_K]

How may I check if the Script Includes is called? I think it could be the issue...?

[Shubham26]

Hi @dev_K 

You can put logs in your script include function and then execute again and see the log are generating or not.

Please mark my answer correct/helpful if it resolved your query.

Thanks,

Shubham Gupta

[dev_K]

After inspecting the page I noticed this error pops up only when using the catalog item on the backend:

just FYI, the list of options for the security wones depend on the selection of the environment

[josgarcia]

Hello, I have the same exact issue. I am using a customized CatalogUtils script include and multiple different Client Scripts that filter off of their previous drop downs.

Did you find a solution? I know that some API’s on the backend are different for what works on the ESC, but I can’t figure out how to get it to filter properly within the backend.