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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hi,
I have a table in the folowing format (in reality there are many more rows and columns with various account types):
Region | Age | Account 1 | Account 2 | Account 3 | Account 4 | Customer count |
London | 35-45 | Yes | No | Yes | No | 13 |
North East | 55-65 | No | No | No | Yes | 10 |
Midlands | 75+ | Yes | Yes | No | Yes | 5 |
I'd like to combine all of the account columns in to one, so I can create a slicer with a dropdown for each account type. This would then let me select total customer who have 'account 1' OR 'account 2'.
I should also mention the data is aggregated, hence the customer count. The only solution I have found so far is to:
1. Open Power Query
2. Add an index to the table
3. Reference the table and keep the relevant account(s), index and customer count columns
4. Unpivot the account columns
5. Load in to the main view, connect the new table to the base table and then create a slicer from here
The main draw back with this method is the file becomes huge. I wonder if there is any other solution?
I'd also like to know if there's a clean way to allow people to select customers who have 'account 1' AND 'account 2'. Currently I just have seperate 'Yes' or 'No' slicers for every account type.
Solved! Go to Solution.
Hi @fionamann_
The solution that you found with unpivot is a best practice.
Because the table for analysis should be "vertical" not only to use desired slicers.
Please refer to the first sections of the linked article :
https://zebrabi.com/guide/how-to-unpivot-data-in-power-bi/
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Hi @PhilipTreacy
I didn't suggest going to the Zebra BI site and learning from them in a general way. Instead, I provided a brief response along with a specific reference link. I believe these two paragraphs effectively summarize the issue. If you have a better alternative, please suggest it. I don't see any advantage for the post owner in your criticizing my answer.
Hi @fionamann_
The solution that you found with unpivot is a best practice.
Because the table for analysis should be "vertical" not only to use desired slicers.
Please refer to the first sections of the linked article :
https://zebrabi.com/guide/how-to-unpivot-data-in-power-bi/
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
I've seen articles on that Zebra BI site that are AI generated and just plain wrong. I'd be very hesitant sending anyone there to 'learn' from what may be incorrect information.
The articles are also overly long and waffly, just text, no helpful images, no video. People would be better off searching for a video or other source that is better.
Phil
Proud to be a Super User!
Hi @PhilipTreacy
I didn't suggest going to the Zebra BI site and learning from them in a general way. Instead, I provided a brief response along with a specific reference link. I believe these two paragraphs effectively summarize the issue. If you have a better alternative, please suggest it. I don't see any advantage for the post owner in your criticizing my answer.