e-geist opened a new issue, #22979: URL: https://github.com/apache/superset/issues/22979
Hi, we experienced that using required filters in Dashboards that cascade/depend on each other with "first value" as default lead to invalid filter combinations upon first dashboard load. If a filter "events" exists whose values are defined as dependent on a filter "year" and both filters are - required - set to "Select first value by default" upon loading a dashboard, the first value in the filter "year" will be picked (as supposed) and the first value in the filter "events" will be picked - even if the event doesn't exist for the picked year. The Charts are then queried with this invalid filter combination and lead to "No data" - until the user fixes the picked filters. #### How to reproduce the bug 1. Create a dashboard with two filters and some charts these filters are applied to 2. Make both filters required and "Select first filter value as default" 3. Make one of the filters dependent on the other 4. Make sure the first value of the dependent filter is not available with the first value of the other filter 5. Load dashboard in UI 6. First value of both filters is chosen automatically -> invalid combination of filters is chosen -> "No data" in charts ### Expected results The dependent filters' value is chosen dependent on the other filters' value - so: First value of first filter is selected -> second filters' values are filtered according to first filter's value -> second filters' filtered list is used to choose first value ### Actual results Both filters' values are chosen indepedently from each other. ### Environment - browser type and version: Firefox - superset version: 2.0.1 - python version: Python 3.8.12 - any feature flags active: nothing too special - we use embedding dashboards, but this also occurs for normal dashboards ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [x] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [x] I have reproduced the issue with at least the latest released version of superset. - [x] I have checked the issue tracker for the same issue and I haven't found one similar. - [x] I have asked other people in Superset Slack - it seems to be reproducible also for others (see here: https://apache-superset.slack.com/archives/C016B3LG5B4/p1675352073631509) If you have any further questions or anything is unclear, please let me know. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
