-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashboard Filters #3015
Comments
Just to add to this -- resizing the browser window after applying a filter will cause the Filter Box to re-render and only display the relevant subset of options in the other filters. I think one of the issues that would be encountered here, particularly with Instant Filtering enabled, would be that further input from the user would be blocked after each selection. |
ahh good spot I didn't notice that on the resize. |
We need to address all this more explicitly. The behavior that @kelchm described is a bug as far as I'm concerned. In the meantime, to fix that, you can add the slice_id of your filter box to the Until we improve FilberBox to allow for explicitly define "cascading filters", you can do so by using the features described in the link above. For instance you can have 2 "Filter Box" and have the first one immune to filters issued from the second one. This may not provide the layout you want but it works... |
Ahh your comment also made me realise i'm dumb for putting all my filter fields in one filter box, by having a separate field in each separate slicer it works like I was aiming for, it just looks ugly lol |
Notice: this issue has been closed because it has been inactive for 293 days. Feel free to comment and request for this issue to be reopened. |
#12148 |
When you add a dashboard filter visualization it works fantastically at filtering, however it doesn't filter itself, so if you have multiple fields, once you select a filter on a parent field, the child fields should only show available results from your filtered dataset instead of still showing the full dataset which then can result in no data for your slices.
The text was updated successfully, but these errors were encountered: