choice list with different sys ids but same values servicenow

Khanna Ji
Tera Guru

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?

1 ACCEPTED SOLUTION

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 🙂

View solution in original post

17 REPLIES 17

Whatever changes it might be where there it is a choice list or a business rule etc. it works based on the sys_id when you move it through update sets/ 

You are so wrong in case of choice list.

In case of choice list, system will clean up entire choice list records and update it with new records because even if you make any changes to a single record in a choice list, it captures the entire choice list definition.

That is why value of a choice matters and not sys id in case of choice list.

You must be kidding me!! What release are you on?

Jakarta. Try it yourself buddy.

We have,  I don't know about abhinay but I have been working with ServiceNow since the Calgary release.  When it comes to updates sets it uses the sys_id so if they do not match it will created a new even if it duplicates the values.