Record from scoped table is added to global update set

[sieusaopolo15]

I have an scoped table and I want to add records into my scoped update set, why does the scoped update set has to be split into global update set and scoped update set to contain the records. What can I do to make the records are added to my scoped update when I click "Add to update set" ?

[SohamTipnis · Accepted solution]

Hi @sieusaopolo15,

This happens because update sets follow the record’s application scope, not your action. Even if you click Add to Update Set, ServiceNow will put records into Global or Scoped update sets based on where they belong.

Your scoped table records go to the scoped update set, but related configs (like UI/form changes) often belong to Global, so they go there.

You cannot force global records into a scoped update set.
To minimize this, always work in the correct application scope and use Studio, but some split is normal and expected.

Let me know if this works!!!!

You can also refer to the below documents to get a more clearer idea.

https://www.servicenow.com/docs/r/zurich/application-development/system-update-sets/system-update-se...

https://www.servicenow.com/docs/r/zurich/application-development/decision-tables/decision-table.html

If you find my answer useful, please mark it as Helpful and Correct. ‌‌‌😊

Regards,
Soham Tipnis
ServiceNow Developer ||  Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10