- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 10:55 PM
Hi Community,
I'm experiencing weird behaviour of a choice type field. The field choice options disappears when user clicks on 'Save as draft' .Otherwise, the options are visible everytime.
Before clicking on 'Save as Draft' UI Action:
Before clicking on 'Save as Draft' UI Action:
Save as Draft UI Action:
Please note that there is no scripting controlling the choice options of this field.
Can anybody please help what could be the iissue?
Thanks,
Ankita
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2025 01:20 AM
I could see that it's a list type field and is it bringing in choices from some table's field?
What happens when you manually save without the button?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 11:15 PM
Hi @Ankita Kolhe ,
he issue could be due to how the server-side update (current.update()) is being handled before the client-side rendering of the form is complete. This might be causing the client-side to miss out on updating the choice field with its dropdown options when the page reloads.
Use the GlideForm (g_form) methods to refresh the field on the client side after the form reloads.
You could try setting the field’s options manually after the form reload, using g_form.setValue() to reset the choice value.
After the form reload, try using a g_form method such as g_form.clearOptions() followed by g_form.addOption() to re-populate the dropdown list options explicitly on the client side.
Check for any UI Policies or Client Scripts that may be dynamically manipulating this field or its options based on the record’s state.
Disable these scripts temporarily and check if the issue persists.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 11:24 PM
Hi @Ankita Kolhe ,
Solution:
Based on the dictionary Entry the field was created on the cmdb_ci_pc_hardware table but the choice list specification table was configured on the alm_hardware table:
Therefore all that was required was to go to the alm_hardware choices table and then I had to add the choice there:
EX:
please do accept this solution if you have found out helpful as this helps me to stay active in this platform and grow accordingly
THanks,
Abin chacko.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 11:41 PM
any business rule is clearing that field since your UI action is updating the state value on that record?
Is that choice field a custom one or OOTB one?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 11:42 PM
Would you mind closing your earlier questions by marking appropriate response as correct?
Members have invested their time and efforts in helping you.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader