Problem with related slicers

[juanrarodriguez]

Hi all,

I am having some troubles (may be a PowerBI bug?) with the data selection that appears in two slicers that I need to add to my Dashboard. I will try to explain the situation, it would be very appreciate if you can help me with any possible explanation 

I have two columns, which have relation between each other.

Column1             ->            Column2

A                            ->            1,2,3,4

B                            ->            5,6,7

C                            ->            8,9,10,11

Knowing that “Column1” target “Column2”, but “Column2” do not target “Column1”, we have these results, when both columns have selected the ALL option in the slicers.

If we select one value of “Column1”, the slave-slicer “Column2”, show us only values with direct relation to “Column1”.

That is correct.

The bad thing comes, when we change values in “Column1”, having values in “Column2” selected. In this case, we have this result.

And that is not correct, because “Column2” value number “3” is not represented in “Column1” value “B” (it belongs to value “A”).

My questions are; it exists any way to update “Column2” selections, when we select different values in “Column1”? May be it is achievable with hierarchical relationships other similar options?

Thanks in advance for your response.

Sorry for my bad English, it is not my mother language

Power BI Report

[cnweke]

Thank you for the screenshots and explanation.

What is happening is normal. Slicers are actually AND statements. Essentially what your slicers are doing is:

show me a record where Column 1 = A and Column 2 = 3.

That record doesn't exist.

Now, onto your main question which is dynamic slicers. That's possible if they are in separate tables (not just columns) when you create a relatonship you need to select a filter direction. If you select bidirectional filters, your filters become 'dynamic'. 

If you're going to use Bidrectional filters in complex models do read up on https://www.sqlbi.com/articles/bidirectional-relationships-and-ambiguity-in-dax/?platform=hootsuite though.

[juanrarodriguez]

---

@cnweke wrote:

Thank you for the screenshots and explanation.

What is happening is normal. Slicers are actually AND statements. Essentially what your slicers are doing is:

show me a record where Column 1 = A and Column 2 = 3.

That record doesn't exist.

Now, onto your main question which is dynamic slicers. That's possible if they are in separate tables (not just columns) when you create a relatonship you need to select a filter direction. If you select bidirectional filters, your filters become 'dynamic'. 

If you're going to use Bidrectional filters in complex models do read up on https://www.sqlbi.com/articles/bidirectional-relationships-and-ambiguity-in-dax/?platform=hootsuite though.

---

Hi @cnweke ,

Thank you for your quickly response. I have read and tested you solution, but unfortunely it didn't work :(. 

It filters well, but is not deselecting the actual selection on the second slicer when changing the values of the first slicer. I attach you the new version, let me know if I did something wrong or if you have another good idea.

Power BI Report

---

---

Thank you!

[cnweke · Accepted solution]

This is the normal behaviour of slicers in Power BI sadly. You're not doing anything wrong.

[juanrarodriguez]

---

@cnweke wrote:

This is the normal behaviour of slicers in Power BI sadly. You're not doing anything wrong.

---

Okay, thank you so much for confirm it 🙂

Regards!

---