ServiceNow best Practice for Choice Value Remapping in Dependent Choice Lists (Reuse Value)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
8 hours ago
Hi,
I have a question regarding ServiceNow Choice records and state mapping updates.
Currently, for the 'state reason' field on problem task table, I am remapping existing choice values to new values.
Instead of making the old choice record inactive and creating a new choice record, I am directly updating the existing choice value to the new value.
Because of this approach, the same choice value can exist under multiple records, with the only difference being the Dependent Value (state).
For example: state reason - 'Out of scope'
- State 4(Pending) → Value 15 → "Out of scope"
- State 7(Resolved)→ Value 15 → "Out of scope"
So the choice value remains the same, but it is associated with different dependent values.
My question is:
Is it considered a best practice to have the same choice value used in multiple Choice records when the dependent value is different, or should the old mapping be inactivated and a new Choice record be created instead?
Are there any potential issues with reporting, scripting, upgrades, data integrity, or choice resolution if the same value is reused across multiple dependent values?
I would appreciate any guidance or recommendations based on your experience.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Hi @Ananya12
Reusing the same value under different dependent values (for example, 15 = "Out of scope" for State 4 and State 7) is fine. It's a normal out-of-the-box pattern. Keep the label identical, because lists and reports look up the label by value.
Changing the value of existing choices is the risky part. Old records keep the old value, so they show the raw number and drop out of filters and reports. Scripts, flows and reports that check the old value stop matching. If the choices are out-of-the-box, editing them also means they're skipped at upgrade.
Best practice is to add new choices and set the old ones to Inactive rather than remapping. If you must change values, migrate existing records with a fix script.
If this helps, please mark it as helpful.