The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I have 2 multi-select slicers: projects and buildings- based on 2 tables:
Project table
ProjectId -primary key | ProjectCode |
1 | P1 |
2 | P2 |
Building table
BuildingId -primary key | BuildingCode | ProjectId -foreign key |
1 | 1 | P1-B1 |
2 | 1 | P1-B2 |
3 | 1 | P1-B3 |
4 | 2 | P2-B1 |
The tables are related:
Project table :Building table: one to many (1: *)
If I select these values in the two slicers
Project Slicer | Building Slicer | |||
x | P1 | P1-B1 | ||
x | P2 | x | P1-B2 | |
P1-B3 | ||||
x | P2-B1 |
When I deselect project P1, I want(expect): the building P1-B2 will disappear
Project Slicer | Building Slicer | |||
P1 | x | P2-B1 | ||
x | P2 |
But the reality is other:
Project Slicer | Building Slicer | |||
P1 | x | P1-B2 | ||
x | P2 | x | P2-B1 |
Is it possible to achieve what I expect?
I did the same as your exemple. and works fine.
Hi, @LeandroDeodato
I want when the project 1 is deselected => the buildings for the project 1 to disappear
Look the table below the slicers... in the slicer "building code" the value P2-B1 remain because is selected, but dont show in table values.
Hi, @LeandroDeodato !
Thank you for your answer!
Sorry, I don't understand your comment... Are you saying this is expected behavior?!
My understanding and expectations may have been influenced by cascading parameters in paginated reports.
Slicers work in a cascade, but if a value is selected and it is not part of the cascade, as soon as you remove the selection from this item, it will disappear from the slicer.
Sorry, my english is horrible.
Hi, @LeandroDeodato !
Thank you for your answer!
Are you saying this is expected behavior? Yes or No 🙂
Yes. unfortunately. if you use a one selection slicer, maybe this dont occurs, but i dont know if you can do this in your report.
show you related please. you have a foreign key in Building table, but dont have this key in project table. try create a key with project code in Building table and related.
Hi, @LeandroDeodato
Sorry, my writing mistake : I changed the names of columns
Project table
ProjectId -primary key | ProjectCode |
1 | P1 |
2 | P2 |
Building table
BuildingId -primary key | ProjectId -foreign key | BuildingCode |
1 | 1 | P1-B1 |
2 | 1 | P1-B2 |
3 | 1 | P1-B3 |
4 | 2 | P2-B1 |
The relation is by ProjectId in the two tables