- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2017 02:43 AM
Hello experts,
I have one role and one user, whenever i am going to assign user to particular role then it's not being capture in my current update set.
can anyone please suggest what can i do in this case ?
Thanks
Nihar
Solved! Go to Solution.
- Labels:
-
Service Level Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2017 03:14 AM
Yes, that is assigning roles to a user, will not be captured in update set. If you create/update a role that ll be in your update set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-16-2018 06:14 AM
Hi Nihar,
Any update on this?
Can you mark my answer as correct, helpful and hit like if you were able to achieve the requirement. This helps in removing this question from unanswered list and helps users to learn from your thread. Thanks in advance.
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2017 02:55 AM
Hi Nihar,
Role creation, updation and deletion is captured in an update set.
Adding role, removing role from user are not captured.
Because of following.
any table data to be captured in an update set needs to have this attribute in the collection type of field.
update_synch attribute has to be set to true.
screenshot belows
1) go to sys_user_role.list and configure dictionary
for the sys_user_has_role table this attribute won't be present so it is not captured.
assigning roles/deleting roles can be manual activity when code is moved to higher instance instead of capturing those in an update set.
Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2017 05:04 AM
Hi Nihar,
Any update on this?
Can you mark my answer as correct, helpful and hit like if you were able to achieve the requirement. This helps in removing this question from unanswered list and helps users to learn from your thread. Thanks in advance.
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2017 04:18 PM
Hi Nihar,
you can force it into an update set (We have a custom UI link to do this), you would add the record for sys_group_has_role. I have seen challenges in doing so in the past. It does not like these records being forced and you get wierd behavior with roles and memberships. I would suggest you do roles and group memberships in production. This will give you the most stable user experience in your production environment.