Need Separate Update Set for Every Application?

[GeoffreyOptumOp]

I'm configuring ITSM Agent Workspace.  I want for my List Categories to be in alphabetical order.  So I want to set all of these order values to the same number so that ServiceNow will use the Names for ordering rather than the hard-coded order values.

However these records are from 5 different Application namespaces.  Do I really need to open up 5 different Update Sets to capture my changes?  That seems like a monumental pain in the a$$.

Since when are records in the Same Table from multiple applications?

Or am I being an ID10T?  Thanks.

[Mark Roethof]

If you are working on for example some HR changes, then it might be in the HR Service table, though also Record Producer table, Variables tables, maybe also a Flow or Business Rule, etc.. That probably is in Human Resources: Core scope. When working on for example a portal form for Submit an Incident, then you would also be working on Record Producer, Variables, maybe also a Flow, etc.. Though most likely... not Human Resources: Core scope, though different scope or even global.

So several changes in the same table, though different Application scopes.

Or several changes concerning a certain application, all in the same Application scope and not in a scope for every separate table.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020-2022 ServiceNow Community MVP
2020-2022 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

[Josh Petrick]

It is kind of a pain, but one thing that helps is update set batching.  You can batch them together even if they're in different applications.  When I run into this situation, I create one update set in the Global scope to use as the parent for all of the rest.  It doesn't make the creation any easier, but it helps when deploying those changes to production.

[GeoffreyOptumOp]

@Josh Petrick Yes, I'm familiar with Parent Update Sets, but this is just silly that I have to do so much manual work to change the order that things appear in a list.  Why can't update sets span applications? 

[Allen Andreas]

Hi,

The incident table, even that, could have non-global fields. You can create a field on the incident table from another scope. So then that incident table has global records AND a record from another scope, just as an example beyond what you're already seeing.

An update set "can" have updates from another scope in it...but...when you preview that update set on another instance, it'll fail and tell you you can't proceed. This is due to how ServiceNow commits updates and the package as a whole. This is standard developer 101 stuff (just saying that it's not some edge case scenario, it's how it works and how we all work with it).

So yes, if you're adjusting records from other scopes, each update set will need it's own. It takes about 3 minutes to switch a scope, make an Update Set for it, make the change, and move on.

Since you said you knew about parent sets, that's good. So make a global parent, associate the child sets, export the parent, preview, commit, and move on.

Please mark reply as Helpful/Correct, if applicable. Thanks!