Auto populate feature is erasing variable value after submit

[dvelloriy]

Hello All,

We have a catalog item with 2 reference variables. One variable is Manager and other is Director.

Manager is present in a variable set (auto populated by requested for's manager) and getting auto populated using below ref qual script:

javascript:new global.TaskUtils().GetActiveManagerList() + "^sys_id!=" + current.variables.requested_for;

Director is a separate variable.(auto populated with Manager's Manager) using auto-populate feature.

Screenshot below

When i create the request, i see both manager and director values getting auto populated, however when i submit the form, director value is erased.

Please assist.

[Brad Bowman]

Is Requested for populated by the user manually selecting a record, or a default value, or a script? Do you have any onSubmit Catalog Client Scripts that might be affecting this variable?  Which release/patch are you on?  To clarify, your reference qualifier on Manager is not auto populating that variable, rather limiting the choices, which you don't even really need to do if you have a script that is auto populating the value.

[dvelloriy]

Hey Brad, 

Coincidence, i was just checking some of your articles on the same issue 🙂

Requested for is also auto populated. 

Release: vancouver-07-06-2023__patch9-hotfix2b-07-22-2024

i think we have a catalog client script which is setting the Manager value.

[Brad Bowman]

I saw this in the Utah release when either the dependent question or the auto-populated variable were updated via script, but I think that was fixed in a patch before Vancouver.  If you change the Requested for, then the Manager and/or Director changes does Director stay after submitting the request?

[dvelloriy]

Yes if i change the director value manually, it stays after submission.

However if we dont change and keep the default value. then gets erased.