elishiacharlick-collab opened a new issue, #44008:
URL: https://github.com/apache/superset/issues/44008
### Bug description
When using cascading (dependent) native filters on a dashboard, changing the
selected value of a parent filter successfully updates the available dropdown
options of the child filter, but does not clear or reset the active/visual
selection of the child filter.
This leaves the child filter showing a stale, invalid value that does not
belong to the new parent's option set. Consequently, the dashboard attempts to
run queries with an impossible combination of filters (e.g., Country = UK and
City = New York), causing all charts to turn blank.
To Reproduce:
1. Create a dataset containing a parent-to-child mapping (e.g., Country
and City columns):
* USA → New York, Los Angeles
* UK → London, Manchester
2. Add two Native Filters to a dashboard:
* Filter 1 (Parent): Country
* Filter 2 (Child): City (configured with the setting: “Values are
dependent on other filters” and set Country as the parent filter).
3. On the dashboard, select USA in the Country filter.
4. In the City filter, select New York. (Dashboard charts load correctly).
5. Change the Country filter to UK.
6. Observe the City filter.
Expected Behaviour:
When the Country filter changes to UK, the City filter's active selection
(New York) should automatically clear or reset (or fallback to a default option
if configured), because New York is not a valid option under UK.
Actual Behaviour:
The City filter continues to visually show and send New York as an active
filter value, even though New York is no longer in the list of available
dropdown options for UK.
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.11
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [x] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
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]
