- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I have a dashboard displaying Incident data, and I want to add filters for Assignment Group
However, I want these filters to display only values associated with incidents that meet a specific condition.
For example:
Table: incident
Condition: Caused by change = CHGXXXXXXX
Filter: Assignment Group
When I configure the Assignment Group filter, ServiceNow automatically uses the referenced table sys_user_group as the filter source.
As a result, the dropdown displays groups from the Group table rather than only the groups associated with incidents that match my condition.
Expected behavior:
If only three assignment groups have incidents where Caused by change = CHGXXXXXXX, I want the Assignment Group filter to display only those three groups.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @MakhanlalM,
There is no dashboard filter setting that does this dynamically, and understanding why will save you time: a Platform Analytics reference filter builds its value list from the referenced table only - for Assignment Group that is always sys_user_group. You can condition that list on fields OF the Group table, but a dashboard filter cannot run an EXISTS / join check against Incident ('show only groups that have an incident where caused_by_change = CHG...'), and dashboard filters do not cascade - selecting a value in a Caused by Change filter does not shrink the available values of the Assignment Group filter. The two filters are combined with AND when they query the visualizations, so results are correct, but the pick-list itself always contains every group.
What you can do, depending on whether CHGXXXXXXX is fixed or variable:
1. If the Change is fixed for this dashboard (your example): restrict the filter to manually defined available values. Edit the Assignment Group filter and define its available values explicitly - select only the three groups that have incidents for that Change - instead of letting it list all values from sys_user_group. The dropdown then shows exactly those three groups. Also put the condition caused_by_change = CHGXXXXXXX on the visualizations / a fixed dashboard condition, so users cannot clear it away. Downside to accept: if a fourth group later gets an incident for that Change, someone must add it to the filter's values - re-check the list when that is likely.
2. If the Change must be selectable by the user: keep both filters (Caused by Change first, then Assignment Group), accept that the group list will contain extra groups, and note that picking a group with no matching incidents correctly returns no data rather than wrong data. To give users a true 'only groups with matching incidents' experience, replace the free Assignment Group filter with a small visualization on the same dashboard grouped by Assignment Group over incidents (with the Change condition applied) and set it to act as a filter / follow when a segment is clicked - a data visualization only ever renders groups that have matching incidents, which is exactly the behaviour the filter dropdown cannot provide.
So: fixed Change = option 1 (manually defined filter values). Variable Change = option 2 (drive selection from a grouped visualization). Do not spend time looking for a reference-qualifier-style condition on the filter that reaches into Incident - Platform Analytics dashboard filters do not evaluate one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @MakhanlalM ,
I tried this using the Related List Condition in the Platform Analytics filter configuration.
Here is what I configured:
Filter Source: Group (sys_user_group)
Data to filter: Incident → Assignment Group
Under Configure values, I added the Related List Condition:
Related List: Incident → Assignment Group
Condition: Caused by Change is CHG0000001
Minimum related records: Greater than or equal to 1
After saving the configuration, the filter displayed only the matching group (Agent Callback Video Group) in the available values.
This way, you can restrict the Assignment Group filter to groups that have at least one Incident matching your specified condition, instead of displaying all groups from the Group table.
Hope this helps!
Hope this helps! If you find this information useful, please mark it as Helpful and accept it as a solution.
Regards,
Mohit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @MakhanlalM,
There is no dashboard filter setting that does this dynamically, and understanding why will save you time: a Platform Analytics reference filter builds its value list from the referenced table only - for Assignment Group that is always sys_user_group. You can condition that list on fields OF the Group table, but a dashboard filter cannot run an EXISTS / join check against Incident ('show only groups that have an incident where caused_by_change = CHG...'), and dashboard filters do not cascade - selecting a value in a Caused by Change filter does not shrink the available values of the Assignment Group filter. The two filters are combined with AND when they query the visualizations, so results are correct, but the pick-list itself always contains every group.
What you can do, depending on whether CHGXXXXXXX is fixed or variable:
1. If the Change is fixed for this dashboard (your example): restrict the filter to manually defined available values. Edit the Assignment Group filter and define its available values explicitly - select only the three groups that have incidents for that Change - instead of letting it list all values from sys_user_group. The dropdown then shows exactly those three groups. Also put the condition caused_by_change = CHGXXXXXXX on the visualizations / a fixed dashboard condition, so users cannot clear it away. Downside to accept: if a fourth group later gets an incident for that Change, someone must add it to the filter's values - re-check the list when that is likely.
2. If the Change must be selectable by the user: keep both filters (Caused by Change first, then Assignment Group), accept that the group list will contain extra groups, and note that picking a group with no matching incidents correctly returns no data rather than wrong data. To give users a true 'only groups with matching incidents' experience, replace the free Assignment Group filter with a small visualization on the same dashboard grouped by Assignment Group over incidents (with the Change condition applied) and set it to act as a filter / follow when a segment is clicked - a data visualization only ever renders groups that have matching incidents, which is exactly the behaviour the filter dropdown cannot provide.
So: fixed Change = option 1 (manually defined filter values). Variable Change = option 2 (drive selection from a grouped visualization). Do not spend time looking for a reference-qualifier-style condition on the filter that reaches into Incident - Platform Analytics dashboard filters do not evaluate one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @MakhanlalM ,
I tried this using the Related List Condition in the Platform Analytics filter configuration.
Here is what I configured:
Filter Source: Group (sys_user_group)
Data to filter: Incident → Assignment Group
Under Configure values, I added the Related List Condition:
Related List: Incident → Assignment Group
Condition: Caused by Change is CHG0000001
Minimum related records: Greater than or equal to 1
After saving the configuration, the filter displayed only the matching group (Agent Callback Video Group) in the available values.
This way, you can restrict the Assignment Group filter to groups that have at least one Incident matching your specified condition, instead of displaying all groups from the Group table.
Hope this helps!
Hope this helps! If you find this information useful, please mark it as Helpful and accept it as a solution.
Regards,
Mohit