Bug? (Blank) appears for slicers that don't have any blank values
I have reports that show (blank) as a choice in the slicer, despite having no blank values, if its clicked, then all my reports just show nothing at all. I find this to be a bug, please fix!
Instead of annoying a lot of people, I think Power BI could be a little bit more intelligent to show what the mistake is.
I am upvoting for this idea.
Thanks @Adam for raising this.
Jay Soell commented
I did have the same issue and I figured out what I was doing wrong. Not sure if those of you may be doing the same thing. I was using 8 different data sources but I was using them independently of one another. However, when I first set it up I brought in all of the tables at once. Power BI automatically tried to build relationships between each one.
I was getting that None in my slicer because there would not be matches with other tables.
I pulled up the Model located on the left hand vertical tool bar and deleted all the unwanted relational connections.
The None on my slicers went away.
I thought it was a bug too at first, but then I realised that I added an new fact table to my data model where I have records that are not related to the "problem slicer". So the slicer shows "(blank)" when you have records in another table that are not related to any value of that slicers (that is in a different table). Doesn't seem like a bug to me, but it would be a "Nice to have" to be able to not show the "(blank)" selection in the slicer.
please resolve this problem
Yes, annoying bug. But there is a quick manual fix:
1) Drag the slicer field into the Page level filters
2) The default "Basic" filtering should show that there are no actual blanks
3) Choose Advanced and then choose "Is not blank"
This removes the blank option from the slicer and doesn't affect your data since there were no actual blanks.
Heather Aldridge commented
This just started happening to us this month. Was not an issue before.
I have the same problem for the first time...other slicers work fine for me.
This is still an issue. Works fine for one table in my queiries but not others. Still showing (blank) even though there aren't any blanks in the data.
It's a shame that Microsoft can't fix this for over two years.
Same issues here
same problem here
I am too facing the same issue. Please assist to resolve it asap.
still not fixed
Mika Palomäki commented
Same problem here, there is no blanks in the dimensions and still this appears. Definitely a bug and I hope these kind of fixes go "on top of the list" before new features. There is workarounds of course but that's a different thing
Chris Parker commented
Why is MS not commenting on this?
I have the same problem. It's not a good practice to hide blank values with filters reports.
Ali Bahadori commented
That is nasty bug! people can't trust data and you should proof there is no blank, that is bug.
I have the same problem. Its anoying!! Please include the option to REMOVE the BLANK from Data Segmentation objects
Manuel Teran commented
Customers are confused due to this Blank option issue. It is really annoying.