Inactive fields are still visible in the Form View

imranshaik0 · ‎02-24-2026

Hi Community!

Hope you are doing well!

I have inactivated a choice to the field (custom field in the case) as per the Business requirement. When I check it in List view, it is working fine. But when I check it in the Form View, I can be able to select the inactivated Choice in both Native UI and CSM Workspace. I have tried cache.do but didn't help. Can I know what might be the issue here?

vaishali231 · ‎02-24-2026

hey @imranshaik0

If the choice is inactive and not appearing in the List view filter, but still selectable in Form view (Native UI and CSM Workspace), usually one of the following is the cause:

Existing record already has that value
If a record already contains the inactive choice value, ServiceNow will still display it in the dropdown on the form. This is expected behavior. Please test by creating a brand new record and check whether the inactive choice appears there.

Choice defined on parent table
If your Case table extends another table (for example task or another parent), verify whether the same choice is still active on the parent table. Sometimes the choice is inactivated only on the child table but remains active at the parent level.

Check:
System Definition > Choices
Confirm the table name carefully.

Client Script or UI Policy adding the option
Check for any Client Scripts, UI Policies, or Workspace client logic using:
g_form.addOption()
g_form.clearOptions()
g_form.removeOption()

If the option is being added via script, the inactive flag will not prevent it from appearing.

Workspace caching
CSM Workspace sometimes caches metadata differently. Try:

Hard browser refresh

Incognito window

Log out and log back in
************************************************************************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh

View solution in original post

imranshaik0 · ‎02-25-2026

Hi @NeshanthA ,

It was due to client scripts. Thanks for the inputs.