Update set changes to Record Producer not carried through to production

will_smith
Mega Guru

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.

12 REPLIES 12

Nope. I was told I be fired, then shot, then burned (maybe alive) if I committed default. All in a joking manner.


Hi William,



Here is the more info on update set best practices.


Update Sets Best Practices - ServiceNow Wiki


Hehe... It would be kind of fun thou, wonder what would work after you commited default 😃