Remove user from group using update sets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2023 12:17 PM
Hi
So I have a group that have some users that should not be in the group anymore, and I have to make the changes in the developer instance, and migrate it through update sets to the test instance. I have tried to remove them and add the group to the update set, but the group members are not captured. I have also tried to add the users to the update set, and I have not been able to capture the change on the sys_user_grmember.list since once they are removed from the list I can't capture the change.. Does anyone have any idea on what to do?
Regards
Pontus

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2023 12:22 PM
Hi there,
sys_user_grmember is data that is by default not captured in Update Sets. There are some workaround possible, though question also is a bit why? What would be the reason for not handling this data in your production instance instead?
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2023 12:25 PM
We don't have access to production during the development, we only have access to the development and test instances, and they will move all our update sets to production themselves, so I would like a way to get that done through the update sets.
Regards
Pontus

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2023 09:12 PM
There are certainly ways to still add this to an update set. Though for me the Community is also to guide people, and not just about sharing a copy/paste script and scoring another correct answer as quickly as possible. So in this case, for me its like "why?"
Rather than doing this through an Update Set or scripted etc, this is something that should be handled differently. Through an integration, provisioning, manually. If you don't have the rights for this in production, fine... who in the organization does? Or who in the organization is going to maintain this in the future? Etc.
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2023 12:39 PM
It is not 'development' therefore nothing to do with update sets. Who ask you for this to do in update sets dont know snow at all. Adding group members would be possible with some "export to update set" feature - look after it you will find some small xml to import and use. But remove action is not possible here either. Just ask any who has acces to PRD to remove. If you wish to look pro write a fix script for removal on sys_user_grmember table, that would go to PRD with update set an sy has to execute it 🙂 overkill for sure.