Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
I have a column called (Flag Deleted). It is data type true/false and contains 3 unique values True, False and Blank. Using this column as a field to filter on does weird things. When selecting false, a certain KPI re-calculates to consider only non-deleted records because we selected false. However, it still takes the blank values into consideration, which is not desired.
I suspected this to be an issue with the true/false data type, but when converting it to a numeric data type (1, 0 and blank) the issue still persisted. When converting it to a text value, only then the issue was resolved.
Could someone point me in the right direction why Power BI is reacting this way?
The users are unable to filter out records that are ONLY false because it will always include blank.
I think its because of the way the equality operator works. 0 = BLANK() and FALSE() = BLANK() both return true. You could try replacing blanks with -1, that would let you filter for either 1, 0 or -1
I did not know about the them being equal to eachother. However, if you select BLANK() in the filter, you do only get the blank values, not the false ones. It's only the case other way around.
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 42 | |
| 37 | |
| 34 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 65 | |
| 62 | |
| 31 | |
| 26 | |
| 25 |