- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2018 07:53 AM
I have modified choice values of category field on Incident form on Dev and manually added those values on Prod since there were very less number of choices.
Now I have added/modified 20+ choices in category and sub category on Dev and planning to move them through update sets.
My understanding is that, choice list works on value not on sys id. When I commit the changes on Prod, it will replace the entire choice list values with new values from Dev without impacting already existing choices since it works on Values not on sys id.
Is my understanding correct?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2018 09:11 AM
Nice, this is the learning attitude. I am very much thankful and appreciate your comments. Not much people agree with others. You tried it and confirmed.
I agree with you that it is not a best practice but ServiceNow is a beautifully designed tool which handles all the conflicts.
In case of Choice list, it simply deletes the existing records and imports the new choices. So, sys id does not matter here and only the value that is counts since choice list fields only care about values 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2018 07:59 AM
When it is what you select on a form yes it uses the value. However when it comes to moving things thought update sets it is recording the sys_id of the records crated. Since you crated the choices in dev and manually crated them in prod the first time they have different sys_id so the system is seeing them as new record not ones that already exist to be updated. This is why you list got replaced / duplicated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2018 08:03 AM
You are sharing the information of transform maps and update sets.
In case of choice list, system will replace the entire values of field choices with the values of new changes during update set movement. I have checked the xml payload of choice list customer update.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2018 08:02 AM
That is incorrect. It will work based on sys_id. I will recommend to delete the choice in QA and do an XML export of the choices in dev and import them in to QA and prod to make the sys_id's consistent in all the environments.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2018 08:05 AM
Please check it, try it and confirm. I tried it and checking it I am true.
When we make changes in choice list, sys id does not matter since, choice lists for a entire field are replaced with new changes.
