- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2025 02:46 PM
In the past, I've built an interactive cascading filter in reporting that will populate the "Assigned To" list with the members of the selected "Assignment Group."
With Platform Analytics, I don't see those filters anymore. It appears that since one filter pulls from the "Group" table and the other from the "User" table, the option to have Assigned To follow Assignment group isn't displayed.
I've tried creating Breakdown indicators in Performance Analytics so the Indicator sources would be the same, but that's not working. I've tried using the "Group Member" table, but to display the group names correctly, it switches to the "Group" table, which causes the initial issue.
Does anyone know how to create a Assigned To filter that will follow an Assignment group filter and just show the members of the selected group(s)?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2025 05:26 AM - edited 01-08-2025 06:30 AM
I have tried to reproduce what I think you are trying to do, and the issue is that you are trying to create a many-to-many filter. An Assigned To user can be a member of multiple Assignment Groups, and of course an Assignment Group can contain many members. See https://www.servicenow.com/docs/bundle/xanadu-now-intelligence/page/use/par-for-workspace/task/set-f....
Unfortunately, by default you need to be an admin to create a many-to-many filter, due to read access restrictions on the tables sys_m2m and sys_collection. So, you need to ask an admin either to set up the filter for you or to create a new ACL rule that gives one of your roles read access to those tables. (We are investigating changing this access restriction, but we have inherited these tables and their access controls from the Platform and need to consult with other teams before we can go about changing the ACLs.) Anyway, for someone with the right to create an M2M filter, the setup is exactly what you would expect.
Assignment group filter:
- Data source: Group table
- Data to filter: Incident.Assignment Group
Assigned to filter:
- Data source: User table
- Data to filter: Incident.Assigned to
On the Assigned To filter, under Follow other filters:
Filters with table connection: Follow Assignment group toggled on
When you toggle that on, you are offered the use of one OOTB connecting table, Group Member [sys_user_grmember]. Use it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2025 10:20 AM
Have you read through the example at the end of https://www.servicenow.com/docs/bundle/xanadu-now-intelligence/page/use/par-for-workspace/task/creat...?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2025 01:30 PM
I have, but it doesn't solve my issue. That filters groups by Manager. I'm trying to filter group members by group.
For whatever reason, it seems like the "User" table cannot follow the "Group" table. I've gotten close by using the "Group Member" table as the filter source (and that allows me to follow the Assignment Group filter), but when doing that, it returns the SYSIDs of the users, not their names. When attempting to filter the data by Incident.Assigned To, it is greyed out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2025 05:26 AM - edited 01-08-2025 06:30 AM
I have tried to reproduce what I think you are trying to do, and the issue is that you are trying to create a many-to-many filter. An Assigned To user can be a member of multiple Assignment Groups, and of course an Assignment Group can contain many members. See https://www.servicenow.com/docs/bundle/xanadu-now-intelligence/page/use/par-for-workspace/task/set-f....
Unfortunately, by default you need to be an admin to create a many-to-many filter, due to read access restrictions on the tables sys_m2m and sys_collection. So, you need to ask an admin either to set up the filter for you or to create a new ACL rule that gives one of your roles read access to those tables. (We are investigating changing this access restriction, but we have inherited these tables and their access controls from the Platform and need to consult with other teams before we can go about changing the ACLs.) Anyway, for someone with the right to create an M2M filter, the setup is exactly what you would expect.
Assignment group filter:
- Data source: Group table
- Data to filter: Incident.Assignment Group
Assigned to filter:
- Data source: User table
- Data to filter: Incident.Assigned to
On the Assigned To filter, under Follow other filters:
Filters with table connection: Follow Assignment group toggled on
When you toggle that on, you are offered the use of one OOTB connecting table, Group Member [sys_user_grmember]. Use it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 07:01 AM
That was what I needed! I got a role updated and was able to make that work. Thank you!