How to filter list slicer values with another List slicer

[gvlado]

Hello everyone
I have couple of Factories. Each factory has various machines. On each machine can be produced various products.
I would like to have tree visuals (List slicers)  Slicer A fo Factory, Slicer B for Machines, Slicer C for products.
Example/problem:

#1

If I chose Factory 7 in slicer A then in slicer B should be shown only machines that belongs to Factory 7.
Also in slicer C at the same time should be shown only products that can be prduced on these machines in Factory 7.

#2

Also should be reversible - If I chose product in slicer C than in slicer B should be only Machines whic can produce that product and in slicer A should be onyly Factories that can produce its product.

Hope I described problem correctly

Tree slicers with such interactions can be done (until now I did) with Attribute slicer but they are going to cancel/retire/abolish  Attribute slicer, so we have to be ready.

Thanks a lot - you have a coffe when we meet
👻

[jaineshp · Accepted solution]

Hey @gvlado,

Based on my experience with similar requirements, here are the steps that worked for me:

1. Data Model Setup

• Create three separate tables: Factories, Machines, Products
• Establish proper relationships: Factories(1) → Machines(M) and Machines(1) → Products(M)
• Set both relationships to bidirectional cross-filtering
• Verify relationship cardinality is correct - avoid many-to-many where possible

2. Slicer Configuration

• Add three List slicers to your report page
• For each slicer, go to Format pane → General → Properties
• Turn OFF "Show items with no data" - this is crucial for the filtering to work
• Position slicers logically (Factory → Machine → Product flow)

3. Visual Interactions Setup

• Select Format tab → Edit interactions
• Ensure all three slicers have "Filter" interaction with each other
• Avoid setting any slicer to "None" or "Highlight" - keep them all as "Filter"

4. Testing & Validation

• Test forward filtering: Factory → Machine → Product
• Test reverse filtering: Product → Machine → Factory
• Check for any orphaned records that might cause unexpected behavior

5. Troubleshooting Common Issues

• If seeing unrelated items, verify your relationships are active
• For many-to-many scenarios between machines and products, consider creating a bridge table
• Ensure no circular relationships exist in your model

This approach replaces Attribute slicers effectively and should handle your Factory 7 scenario perfectly. The key is getting the data model relationships right first.

Fixed? ✓ Mark it • Share it • Help others!

Best Regards,
Jainesh Poojara | Power BI Developer

[gvlado]

It works with one fact table, but I have 3 fact tables and then I have to use relationship in calculate. Not all relationships can be active because of possible multiple path to the data.
Will se what will I get at the end.
Here  is the model view

Definitely Attribute slicer was much better than List slicer in many options - for now - I hope they will improve List slicer to have at least Attribute slicer attributes

[gvlado]

I'm curious why they didn't implement the functionality like for Attribute Slicer or why they just didn't develop Attribute Slicer more - it was so simple and usable. 😒

[jaineshp]

I had the same thought before.

Glad to know we're on same page.

[gvlado]

wow - so quick answer
You deserve bunch of coffe 👻

[jaineshp]

Hey @gvlado,

Sure will catch up soon!👍