Update set changes to Record Producer not carried through to production
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2016 05:14 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2016 10:24 AM
Nope. I was told I be fired, then shot, then burned (maybe alive) if I committed default. All in a joking manner.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2016 10:27 AM
Hi William,
Here is the more info on update set best practices.
Update Sets Best Practices - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2016 10:30 AM
Hehe... It would be kind of fun thou, wonder what would work after you commited default 😃