null boolean value lumped in with false by slicer

[rynhowl]

I have a boolean column that is sometimes null, and I have a slicer in my report for that column. The slicer shows "True", "False" and "(Blank)" as options, but selecting "False" includes the "(Blank)" values as well. I want to be able to view data where this is explicitly set to false. Why is the slicer showing separate options if they are equivalent in filtering?

[v-gizhi-msft · Accepted solution]

Hi,

After my test, i think it is a deafult design that if not True, return False regardless of whether is blank or not.

In other words, False includes Blank.

Best Regards,

Giotto

[v-gizhi-msft]

Hi,

It is because Blank() and True()/False() are different data type.

I did a test, see this:

In this sample, i define a policy for values, and you can see in the above screenshot, the values that lower than 100 is not defined and should return blank, but still return false.

When you add a new definition to values that lower than 100, it will cause data type error.

See my attached pbix file.

Best Regards,

Giotto

[rynhowl]

Thanks, but this isn't quite the issue I'm having. I'm importing data that has a boolean column, and some of that data is null. So the values in the column are TRUE, FALSE, or NULL. If I create a slicer on that column, it automatically lists all the values in the column, TRUE, FALSE and (Blank) which seems to be the replacement for NULL.

If it is going to display (Blank) as a separate value, it should treat it as a separate value. If it doesn't treat it as a separate value, it should be fixed so that it does. It seems like a valid filtering option, "Show me only data where this value is not null".

[Anonymous · Accepted solution]

Hi, I know this post is from several months ago. But, I figure someone else is going to run into this and want an actual solution. I did a workaround where I added another text column for display with values: 'True', 'False' and null. The slicer works correctly based on that text column.

[v-gizhi-msft · Accepted solution]

Hi,

After my test, i think it is a deafult design that if not True, return False regardless of whether is blank or not.

In other words, False includes Blank.

Best Regards,

Giotto

[Greg_Deckler]

So, what is the data type of your slicer column, boolean?

It could be that the blank is getting thrown in there because there are non matching rows in some connected table.

[rynhowl]

The column I'm using for the slicer is type "True/false". Is there a "boolean" type I'm missing, or is it just the "True/false"?

The only other table I have is a single value with the date, so I don't think it's a issue with other tables.