Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
I have a report with 3 columns of attributes that I would like to combine into one multi-selectable chiclet-style slicer, since they are all somewhat similar ways to filter the data. The first has three values, the other two are Yes/No fields. Both of the Yes/No fields are such that there would never be a reason to focus on the "No" values, only the "Yes" ones. Here is an example similar to what my data looks like.
Right now, I have 3 chiclet slicers. If using my example data, the first has "Job" and has three chiclets for "Sales", "Finance", and "Operations". The other two each have two chiclets for "Yes" and "No". As I mentioned, there isn't even a need to have the "No" options, and having to use 3 chiclet slicers is cluttering up my report (This is a really large dataset with several other attributes to filter down as well).
I want to have one slicer where the user can select multiple options. What I envision would be a slicer titled "Empl Type", with buttons for "Sales", "Finance", "Operations", "Day Shift", and "Salaried". I've asked around amongst the other engineers I work with, and no one's figured out how to make this work.
If there isn't a way to do so, does anyone have an idea for at least removing the "No" options from the two "Yes/No" slicers? I could then set up the report with the three slicers so that they sort of look like just one.
Solved! Go to Solution.
Couldn't figure out exactly how to do it like I thought I wanted, but the end result works great!
I left as three separate columns, with a single character designating the type. I set the two "Yes/No" columns from my query to either have the value, or be null. Then, I created three new tables with the short characters used in my main data table, along with "prettified" names for use in the slicers. I set the relationships to crossfilter both ways, and created three slicers, but grouped them together so they looked like they belonged together. Creating the extra tables eliminated buttons showing for both "Yes" and "No", and now it will either filter it to the equivalent of the "Yes" answers, or not filter that column at all.
How about creating a new column and filter against this column?
Column = IF('Table'[Day Shift]="Yes"&&'Table'[Salaried]="Yes",'Table'[Job]&"--"&"Day shift"&"--"&"Salaried","Other")
Couldn't figure out exactly how to do it like I thought I wanted, but the end result works great!
I left as three separate columns, with a single character designating the type. I set the two "Yes/No" columns from my query to either have the value, or be null. Then, I created three new tables with the short characters used in my main data table, along with "prettified" names for use in the slicers. I set the relationships to crossfilter both ways, and created three slicers, but grouped them together so they looked like they belonged together. Creating the extra tables eliminated buttons showing for both "Yes" and "No", and now it will either filter it to the equivalent of the "Yes" answers, or not filter that column at all.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
147 | |
85 | |
66 | |
52 | |
46 |
User | Count |
---|---|
215 | |
90 | |
83 | |
66 | |
58 |