Why are my fields defaulting values that don't exist?

[simran3]

I removed certain choices from a select box, and on the catalog item it is not showing those choices anymore. But when I added the catalog item to an order guide - for some reason those choices that do not exist, are the default value on the field. Here's a screenshot of the variable set on the order guide.

New ID and System Access do not exist as choices for those select box variables anymore, but for some reason, as soon as I land on this page on the order guide - it defaults to those choices and it confuses users.

Here is a screenshot of variable set on the catalog item by itself:

Here it is acting as it should, default value should be --None--. Why is it behaving differently when added to an order guide?

[Sandeep Rajput]

@simran3 Could you please check the client scripts and UI Policy associated with Order guide is responsible for this? It looks like a client script is adding these options on the fields on order guide.

Hope this helps.

[Brad Bowman]

Does the order guide have the variable set as well, or when you go to the Choose Options / Next screen is that the first time you see these variables?  Are there any Catalog Client Scripts or scripted Catalog UI Policies on the Order Guide?  In the Rule Base of the Order Guide which includes this Catalog Item, do you have Item Variable Assignments?