Re: Interaction between two Slicers doesn't work w...

Erin · ‎09-27-2016

Hi All,

I have two slicers(S1 and S2) with some visuals on one report , S1(City) and S2(Product), and S1 can control S2 but S2 can't control S1. S1 and S2 can control all other visauls. The interaction doesn't work properly when you unselect a selected item in S1 while there is a selected item in S2 related to this S1 item, and that S2 item will display as selected( will not disappear) but not work as a filter on visuals on the report.

E.g.:

2 cities in S1, C1 and C2

2 products in each city: P11, P12 in C1, and P21, P22 in C2

failed scenario:

in Slicer1, select C1 and C2, then 4 products P11, p12, P21 and P22 display in Slicer2;

in Slicer2, select P11 and P21, and everything works well so far;

then go back Slicer1, unselect C2, in Slicer2 I can see P22 disappears but P21 is still there selected as well as selected P11, and visauls display only P11 data (without P21 data).

by my understanding, after unselecting C2 from Slicer1, all items related to C2 should not be listed in Slicer2 since Slicer1 works as filter on Slicer2. The current result causes confusion on the report.

I am not sure if there's any settings I need to change to make it work properly or it's just a bug.

Thanks!

ishaaa2709 · ‎04-04-2024

I have a similar issue, not sure if there is any solution till now.

I have a date table and columns - date , Period.

I am using 2 slicers on the same page. Date is used as a range slicer and Period is used as a dropdown.

When I select any period from the dropdown i.e. FY2022, the dates do not filter accordingly.

The interaction between the two slicers is on and both columns are coming from same table.selection in dropdown - 2022, but above date range not updating

Marco57 · ‎01-30-2021

Is this bug still here? I also have an issue between two slicer ranges not interacting with each others by defaults. Slicers are in between mode and only if I tell them to visually interact together, they would update otherwise ranges excluded by the first slicer would still show up on the second one. Issue is I use BI Embedded and I can't edit interactions programatically as the API does not support it.

v-haibl-msft · ‎10-09-2016

@Erin

I‘ve got the response from Power BI team. This is by design.

We store previous selections and show them regardless of whether another filter may hide them. We do not want to clear selections based on filter from other slicers, and we are obligated to show any seleted items.

Best Regards,

Herbert

Erin · ‎10-24-2016

@v-haibl-msft

Could the team explain to us why this is by design? By my understanding, if the selection on higher level filter is unseleted, it means the user no longer needs data under that selection hierarchy, and also means the previous selection on lower level filter is not longer needed too.

Thanks

sanjayshah · ‎12-26-2016

This clearly seems to be a bug. Request the PBI team to explain why it is "by design"...? Generally slicer values from the same table are dependent on selections. Lets say that a table contains both countries and cities. If i select a country, i see only the cities pertaining to that. Now if i select another country, it should show cities of the new country, it should not continue showing the city of the previous country !!

Sanjay Shah

Prosys, Pune, India

sanjayshah · ‎12-27-2016

Hi Qiuyun :

Thanks for your reply.

Sorry, but I don’t agree with you. Let say that I have selected Year 2016, Quarter 1 and the Month slicer shows Jan, Feb and March. I have now selected March and the dashboard is showing the required numbers. Now if I select Quarter 2, do you mean that April, May and June along with March will be shown ?

This may not be a “technical” bug, but seems to be a usability bug.

Regards

Sanjay

v-haibl-msft · ‎10-24-2016

@Erin

Please refer to my last post for the explanation from PBI team. In this scenario, unselecting on higher level filter should make the previous selection on lower level filter unselected generally. But PBI now stores previous selections and show them regardless of whether another filter may hide them. The team do not want to clear selections based on filter from other slicers, and they are obligated to show any selected items.

Best Regards,

Herbert

Erin · ‎10-27-2016

Any use cases they use to support this design?

Sean · ‎10-27-2016

@Erin If you remember I was with you on this!

First the bad news!

I think this is more about the principle - you have selected something in the slicers yourself!

Basically you have set the search criteria yourself!

They are not about to undo/clear YOUR selections!

As you can see in the picture you selected Dallas P1 and Houston P1

They don't want to clear your selections - you are the only one that can clear them!

In your example I guess the products are exclusive to those cities and its easier to see why you may not like the outcome.

Hope this makes sense!

If you have not selected something yourself and it does not apply it will disappear

however if you have selected something yourself it will show no matter what because YOU selected it yourself!

And now the good news!

I think I may have found a solution for you =>the Hierarchy Slicer

Hope this helps!

Anonymous · ‎06-17-2017

Hi @Sean & @v-haibl-msft

I think the hierarchy slicer is a good workaround but doesn't really deal with the problem. Also it looks a bit different from the standard slicer so mix and match aren't great - I'll raise it with the developer.

There's a confusing usability effect in the standard slicer. If an item is selected but not valid, then it still appears (as noted) - but at the bottom of the list. If the list is being used and the height of the list is small so that there is a vertical scroll bar, then if the invalid item is selected and operational, you can't see it. I am finding that users report a bug (or get confused), because they can't see it. One partial solution would be to move it to the top of the list.

In terms of logic, I don't think I agree with your approach although the simplicity of the idea is good. I would agree with your approach if cross-filtering is turned off between the two slicers. However, if cross-filtering is active, I expect one slicer to act upon the other slicer. When a slicer item is selected then, on all visuals where the cross-filter is active, filtering takes place. But not seemingly on the slicer. To me, that is not a logical application of cross-filtering.

Erin · ‎10-31-2016

@Sean

Thanks for following and solution...

Hierarchy Slicer may not be a good way for my case. I have a huge data set with the dashboard, and large number of data in each slicer, and want to provide users a good way to see the options they can select from by filters.