Update set changes to Record Producer not carried through to production

[will_smith]

I made some changes to a record producer update set in Dev yesterday and when I rolled it out to production the script was not the most current, and a second record producer I had created, and then inactivated, was active. Would someone help me understand why? This is the 2nd time this has happened - active states flipping; not with a record producer though.

[Goran WitchDoc]

Sounds strange. Is it that the changes isn't save at all or are the found in the default update set?

[will_smith]

Yes, they were in the Default update set. Thanks Goran.

[Travers M]

See, this is easier to do now that they have the update sets hidden and tucked away under the gear menu.   They used to be up at the top of the page so you could see at a quick glance if you were in the correct update set.   We've used a little manipulation to bring this a little more out in the open and it has proven helpful.   The problem is that when you upgrade to a newer version of ServiceNow, this ends up breaking or looking funny.     If you'd like to put this in your dev instance to see if it helps, the steps are at:

Bringing the Update Set Picker back from the UI14 Gear Menu - ServiceNow Guru

This becomes increasingly useful if you're working on multiple update sets at any given time.   After having to move updates around in update sets does make you pay a little closer attention to the one you're currently in though

[Nani6]

Hi Goran,

Can you help me out in below mentioned thread? Thanks in advance.

https://community.servicenow.com/thread/211773

Thanks

Shrikanth