Why are my Variable Not Saved in Catalog Task or Request Item?

[kwenzel]

Hi,

I have a a variable defined on a catalog item which I want the fulfiller to be able to change later on in the workflow from the Request Item or Catalog Task screen.   I have two issues with the variable:

1.   The variable is defined as a yes/no variable, yet when shown in the variable editor, it display as a simple text box, not as a dropdown with Yes or No selections.

2.   When I go to change the item from "Yes" to "No" and save, my edits don't persist.

Here is a screen shot of the variable editor on the requested item:

What could I be doing incorrectly?   Any hints are appreciated!

Thanks,

Kris.

[kwenzel]

Hi,

the variable is hidden in the catalog view (the one users order from).

I removed the default value specification, yet it still changes back.

[anthony_ciotta]

Kris,

Have you checked to see if there are any Client Scripts on the RITM table that are setting all Catalog variables to read-only?   We have one that does that.

[kwenzel]

Hi - I checked and I don't see any active client scripts defined on the sc_req_item table.

Is there a way to do a global search of all scripts to hunt for code that could be causing this issue?

[anthony_ciotta]

Go to System Definition > Client Scripts.   Edit the filter, add an AND condition of "Script contains XXXX".   The question is what should you search for?

If you add a brand new variable to the form, can you edit it?   I have seen a corrupt variable in the past and needed to recreate it.   Is this the first time you are trying to edit a variable after submission?   or do you have other items that this function is working on?

This article may help locate the culprit.

Readonly Variables on a Standard Form - ServiceNow Guru

[rohantyagi]

Try removing the default value of "Yes" and test.