When the field is set as a number and the value for the field is a 0, than the boolean expression will state that the field with the value of 0 is both blank() as it is 0.
I don't find this logical. Is this an old bug that was never been fixed and now everyone is working around and abusing it, or... is this intended?
The same issue has been reported before internally: CRI 88868161.
"In DAX, the comparison operator = performs equivalence comparison. Since 0 and BLANK are equivalent values, operator = returns true when comparing 0 to BLANK. Users can use DAX function IsBlank to detect BLANK values."
Best Regards,Qiuyun Yu