The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
I have the following star schema in power BI
The report requires a slicer from Dim B. Then a slicer on DimA
Unfortunately the report is a table and there is nothing from the fact table in the table.
When I slice on B I can still see everything in A
I really dont want to set up any multiple directions on the relationships. Is there anything I can do to get this working?
@DebbieE Have my answer solved your problem? If so, can you please accept my answer as Solution to help other members find it faster? Thank you very much for your kind cooperation!
Hi Debbie, I have some twisted logic for you if you would like to go creative:)
Duplicate /Reference your Fact table, remove all the columns except AKey and BKey.
Remove the duplicates. Append the query from Atable, Append the query from B Table, this way you ensure that you get all of the As and all of the Bs irrespective whether they are in your Fact Table.
Then create a primary key in your fact table and in your new table Akey-Bkey.
Remove all the unnecessary columns except Akey Bkey and PrimaryKey.
Disable Load on A, B. Create Relationships Fact TAble and New Table.
Then use Akey from this table and Bkey for your slicers. there will be blanks in both, filter them out on the visual level. and voila:)
Let me know if that works for you.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
114 | |
79 | |
78 | |
47 | |
39 |
User | Count |
---|---|
147 | |
115 | |
65 | |
64 | |
53 |