Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi,
I need to create about 10 different slicers - some of them Toggles (between A and B), some of them Single selection (Either C OR D OR E) and some of them Multiple selection (multiple options can be true - F AND G AND H; only F AND G; only G AND H; only F AND H)
Should I:
1: create different types of tables/queries for different types of slicers:
A) Toggle
B) Single selection
C) Multiple selection
--> 3 tables - one for each type of slicers
2: bunch them together inside one table
--> 1 table
or 3: create a new table for each single slicer
--> about 10 tables...
Bye
Michael
Solved! Go to Solution.
Let go of the Excel mindset and embrace the concept of dimensions and facts. Your filter choice options could be stored in reference tables, implemented as calculation groups, or you could completely drop that idea and teach your users how to modify filters in Power BI.
d) None of the above. Use the standard filter pane. That's what it is there for.
Ok. Got it. In PowerBI I use the Filter-pane.
But before displaying in PowerBI:
If I have an Excel-Table as Source - with Tabs for Toggle, Single and multiple-Selection-Filters - what's the recommended way to structure them? Do I combine them into one tab, do I create a table for each type of Filter or do I create a table for each Filter itself.
Once I prepare them for display in PowerBI (...where I will use the Filter-pane): How do I handle the "empty cells" in Filter_multiple2?
Let go of the Excel mindset and embrace the concept of dimensions and facts. Your filter choice options could be stored in reference tables, implemented as calculation groups, or you could completely drop that idea and teach your users how to modify filters in Power BI.
User | Count |
---|---|
98 | |
78 | |
77 | |
49 | |
26 |