Forum Discussion
Helper IHow to remove (blank) from multilevel slicer
Community ChampionHi LucMarv
Blanks arise due to gaps in the data model. A quick workaround is using the Filter Pane and selecting each field to remove the blank.
1. Click on the visual.
2. Go to the Filter Pane on the right.
3. Click on each of the fields you're using for the slicer.
4. Untick "BLANK".
Hope this helps.
Theo
Helper II just tried your suggested sollution, but it actually removed all the lines with at least one blank... the only remaining items in the slicer are those with all three elements filled:
All the others have disappeared... Any ideas how to fix this?
The gaps in my table are intentional.
- TheoC
LucMarv if there are gaps, there will be blanks unfortunately. Have you thought about creating a separate table with the specific categories and subcategories? Then you can create a relationship from the new table to the Fact table, and use the new table to Slice. The new table can be without blanks?
Otherwise, can you use the logic:
IF GroupingL3 is blank then fill the blank with Grouping L2
IF Grouping L2 is blank, then fill the blank with Grouping L1... and so on?
- LucMarv
Dear TheoC,
When you say:
@LucMarv if there are gaps, there will be blanks unfortunately. Have you thought about creating a separate table with the specific categories and subcategories? Then you can create a relationship from the new table to the Fact table, and use the new table to Slice. The new table can be without blanks?
The table that this slicer is coming from is already a separate table (the tumour grouping is just a simple lookup table that links on the TUMOUR_GROUP_ID variable with the main data).
So the slicer is already made from (what PowerBI calls) a dimension table which is linked to (what PowerBI calls) a fact table.
- TheoC
Hi LucMarv
Apologies, I'm referring to a Dim table that is structured in such a way that blanks don't exist and only the attributes of the specific groups are captured. If you have to have so many blanks, then just break it down further into separate tables that have a one to many off one another back to the fact table.
So, you'd have:
- Level 1 table
- Level 2 table that has columns being Level 1, Level 2 but excludes any Level 2 blanks.
- Level 3 table that has columns being Level 2 and Level 3, but excludes Level 3 blanks.
This way, your Slicer will be Level 1 category from table Level 1. Level 2 category from table Level 2. Then Level 3 category from table Level 3.
Hope that makes sense?
Theo