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" ?

[Dinesh Chilaka]

Hi @sieusaopolo15 ,

Make sure your scoped update is the current update set when you are clicking on the Add to update set related link.
If my response helped ,mark it as helpful and accept the solution.

[Community Alums]

Hi @sieusaopolo15 ,

Attaching the link to the KB article—hope you find it useful.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0867578

Please mark it as helpful if it resolves your issue.

Regards,
Aparna

[lauri457]

Are you adding a record from a table that is 'data' as in the table parent is not application file [sys_metadata]? Only configuration is scoped. The add to update set utility only abuses the update set mechanism to allow moving other types of payloads. 

You can probably force the customer update to your scoped update set with a script but I haven't tested if it gives errors when committing. What is the issue with having a global update set for the data?

[Tanushree Maiti]

1. Set the Application Scope Correctly: Before doing any work, navigate to the Settings (gear icon) > Developer and ensure the Application is set to your scoped application.
2. 
3. or 

   

4. When you click "Add to Update Set" on a record, the system checks if the record's scope matches the current Update Set's scope. If they match, it works correctly.