Select box variable choice value changes to new value but in Ci new value updated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago - last edited 3 hours ago
Select box variable choice value changes to new value but in Ci new value updated but for future records coming separately but we need to coming under same version name
OLD value:
lable:Microsoft office 2024 for VMs server
value:Microsoft office 2024 for VMs server
New value:
Microsoft Office Standard 2024 for VMs Server
Microsoft Office Standard 2024 for VMs Server
issue:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
28m ago
Hi @mani55 ,
Based on your screenshot and description, it looks like you have two groups that appear visually identical but are being split into separate rows. This almost always indicates a hidden byte-level difference in the underlying data.
Here are the three things you need to check to resolve this:
1. Check the XML for Hidden Characters (Most Likely Cause)
Because browsers hide trailing spaces and zero-width characters, you cannot trust what you see on the list view.
Open one CI record from the group of 220, and one from the group of 1.
Right-click the header on both and select Show XML.
Compare the exact string inside your version tags. You will almost certainly find a trailing space or a hidden character in one of them.
2. Verify the Choice Value in the Variable
Navigate to your Select Box variable and review the Value field for the new choice. Ensure there are no accidental trailing spaces at the end of the text. If there is a space in the variable's choice value, every future record will be created with that hidden space, causing it to split from your clean data.
3. Normalize Existing CI Records
If existing records contain a mix of the clean value and the value with a hidden space, they will continue to group separately. Once you fix the variable choice, you will need to update the outlier records (either manually or via a background script) so they perfectly match the correct, clean string without spaces.
Hope this helps you track down the mismatch!
Please mark this answer as Helpful if it resolves your question. 🙂
Thanks,
Yogesh Bhatt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
28m ago
Hi @mani55
Keep the Choice Value unchanged as the existing value, "Microsoft office 2024 for VMs server", and update only the Label to "Microsoft Office Standard 2024 for VMs Server".
This ensures that both existing and future requests continue to map to the same underlying database value without requiring any data changes.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti