Problema com visual Segmentação de Dados / Slicer Bug

[Gnassau]

Ao utilizar o visual Segmentação de Dados no Power BI, percebi que ele não está interagindo corretamente com outros visuais, como deveria.

Por exemplo:
Se adiciono duas colunas da mesma tabela em dois visuais de tabela diferentes, ao selecionar um valor em um dos visuais, o outro é automaticamente filtrado conforme esperado. No entanto, quando um dos visuais é uma Segmentação de Dados, essa interação não acontece, ou seja, ao selecionar um valor na Segmentação de Dados, o outro visual é filtrado corretamente, mas ao selecionar um valor no outro visual, a Segmentação de Dados não é atualizada.

Não entendo por que esse comportamento ocorre apenas com o visual de Segmentação de Dados. Acredito que possa ser um bug.

---

When using the Slicer visual in Power BI, I noticed that it does not interact correctly with other visuals as expected.

For example:
If I add two columns from the same table into two different table visuals, selecting a value in one of the visuals automatically filters the other, as expected. However, when one of the visuals is a Slicer, this interaction does not happen. That is, when I select a value in the Slicer, the other visual is filtered correctly, but when I select a value in the other visual, the Slicer is not updated.

I don't understand why this behavior occurs only with the Slicer visual. I believe this might be a bug.

[grazitti_sapna · Accepted solution]

Hi @Gnassau,

This behavior is expected in Power BI and is not a bug. It happens because the Slicer visual works differently from other visuals in the filtering architecture.

1. Slicer can filter all visuals

2. Visuals can filter other visuals using cross filtering

3. As slicers are global filters they are not filtered on visual filteration

A Slicer is not a regular visual. It is a filter control.

It behaves like a global page filter UI.

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!

[Gnassau]

Thanks for your answer, I've always understood that it wasn't the common behavior, but I think that's ok!

[Irwan]

hello @Gnassau 

Perhaps because of relationship.

if your slicer get a value from a dim table that has one-to-many relationship to fact table, your slicer will be not filtered since the filter goes from dim to fact table and not vice versa.

Thank you.