- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
I am having problems with getting filter source values to apply on a new filter. When I select the Data Source and try to "configure values" the UI has changed and the current option does not seem to work.
When I go through and deselect the options I do not want to appear and save, all 141 options still show in the filter. Configure Values looks similar to below (note, I removed most of the group name):
I have previously created a Filter Group for assignment group and assigned to without issue. The one I previously created looked like this in the "Configure Values" field:
Is there an issue with the functionality or have I missed something/done something wrong?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @Michelle Clover,
First thing to check: what your filter source is actually built on. Your "Tables" field shows Group.Name, which means you're pointing the filter at the Name field on the Group table (a String), not at a Reference field. That's a different Configure values code path than your working Assignment group filter, and it's worth ruling out before you assume the feature is broken.
- Field type: platform analytics selection filters natively support Choice, Reference, Boolean and Date. A Reference field (like your earlier Assignment group filter) opens the real condition builder, "Use existing filter", "Save Filter", "Editor", that runs an actual query against sys_user_group. A String/dot-walked source like Group.Name instead pulls a flat list of every distinct value currently in the data, that's the plain checkbox screen you're stuck on.
- Rebuild against the reference field if one is available (e.g. the Group reference itself, or Assignment group on the underlying table) instead of dot-walking to Name. That should put you back in the same Editor/Save Filter experience that worked before.
- Duplicate-looking rows: the "A", "A", "A", "A'" entries at the top of your 141 values usually mean duplicate or near-duplicate group names (trailing space, case difference, or an inactive group sharing a display value), not a checkbox rendering bug. Worth spot-checking sys_user_group for that group name.
- Confirm the save actually commits: with 141 rows the modal can scroll past the Save action; make sure you're triggering it, not just closing the dialog.
If you rebuild on the reference field and it still doesn't restrict values, that's worth an HI case with your instance version noted, this Configure values modal has been reworked release over release and I can't reproduce your exact behavior remotely.
References
- Filters in Platform Analytics
- Configure a Single/Multiple select or cascading filter
- Filter Configuration in Platform Analytics (Community)
Thank you,
Vikram Karety
Octigo Solutions INC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @Michelle Clover,
First thing to check: what your filter source is actually built on. Your "Tables" field shows Group.Name, which means you're pointing the filter at the Name field on the Group table (a String), not at a Reference field. That's a different Configure values code path than your working Assignment group filter, and it's worth ruling out before you assume the feature is broken.
- Field type: platform analytics selection filters natively support Choice, Reference, Boolean and Date. A Reference field (like your earlier Assignment group filter) opens the real condition builder, "Use existing filter", "Save Filter", "Editor", that runs an actual query against sys_user_group. A String/dot-walked source like Group.Name instead pulls a flat list of every distinct value currently in the data, that's the plain checkbox screen you're stuck on.
- Rebuild against the reference field if one is available (e.g. the Group reference itself, or Assignment group on the underlying table) instead of dot-walking to Name. That should put you back in the same Editor/Save Filter experience that worked before.
- Duplicate-looking rows: the "A", "A", "A", "A'" entries at the top of your 141 values usually mean duplicate or near-duplicate group names (trailing space, case difference, or an inactive group sharing a display value), not a checkbox rendering bug. Worth spot-checking sys_user_group for that group name.
- Confirm the save actually commits: with 141 rows the modal can scroll past the Save action; make sure you're triggering it, not just closing the dialog.
If you rebuild on the reference field and it still doesn't restrict values, that's worth an HI case with your instance version noted, this Configure values modal has been reworked release over release and I can't reproduce your exact behavior remotely.
References
- Filters in Platform Analytics
- Configure a Single/Multiple select or cascading filter
- Filter Configuration in Platform Analytics (Community)
Thank you,
Vikram Karety
Octigo Solutions INC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Ah I see what I did different now. Thank you