Power BI Report two slicers - when first changes, second slicer retains previously selected item

[009co]

I have a  Power BI Report with two slicers.

The first slicer filters data by State. The second slicer shows all Cities within that State.

The Cities slicer is set to be a list with "single select".

When I change the State slicer value to another state, the Cities slicer retains the previously selected State city.

The problem with this is that of course with the State filter on, there is no underlying data for the previously selected city so the report has no data with just looks bad eg lots of "(Blank)" values in cards and all charts are blank.

How can I get the Cities slicer to "forget" and deselect the previously selected State's city? Is it possible? Any tips or tricks?

[MattAllington]

In response to my post, Miguel Myers (MS PM for visuals) says he plans to fix this. For now, the solution I posted works. 

[PowersBI]

Thanks for posting that new workaround -- I plan to try it this week. 

Did Miguel Myers give you any sense for timetable on a better solution? 

[Drishti97]

Hi All,

I have a similar problem like this. Is there any solution for this in latest version?

Thanks

[PaulDBrown]

See if this method posted by @MattAllington in the ExceleratorBI website  works for you:

https://exceleratorbi.com.au/slicer-values-dont-clear-after-changing-a-second-slicer/ 

[PaulDBrown · Accepted solution]

Currently not possible I'm afraid. If a value is selected in a slicer, it remains selected even if filtered by another slicer

[PowersBI]

Circling back to this issue more than a year later -- has there been any update or is there still no solution in sight?  Has anyone figured out a work around? 

I'm dealing with a similar problem where I have one slicer that changes measures in a visual, and a second slicer (toggle) to filter between different units of those measures. 

[009co]

Yeah I guess it was a long shot.

Of course while it is helpful to know that a selection of filters results in an empty set in this context the use case isn't asking for that knowledge.

Feels like a nice option for a slicer, something like "clear slicer selection and select first value of next filtered results set"

It would need to have some programming to make it hop to one of the first slicer value's second slicer values.