Forum Discussion
how to correctly filter blanks
- 9 years ago
Anonymous wrote:
thanks for your answer, but I asked DAX, and you showed M language inside Query Editor.
DAX is used only in the Report view for measures and calculates columns or tables. Inside Query Editor it is M language.
Anyway, if they both commands work the same way, when should I use one or another?
Anonymous
I showed the null and empty("") difference in data model in M(Query Editor) and Data tab in report designer window, if you look into my snapshot carefully.
Though I think they're equal, I'd use BLANK() when I comparing/counting blank values and use LEN to compare text type(Returns the number of characters in a text string) to make my DAX more comprehensible.
thanks for your answer, but I asked DAX, and you showed M language inside Query Editor.
DAX is used only in the Report view for measures and calculates columns or tables. Inside Query Editor it is M language.
Anyway, if they both commands work the same way, when should I use one or another?
Anonymous wrote:
thanks for your answer, but I asked DAX, and you showed M language inside Query Editor.
DAX is used only in the Report view for measures and calculates columns or tables. Inside Query Editor it is M language.
Anyway, if they both commands work the same way, when should I use one or another?
Anonymous
I showed the null and empty("") difference in data model in M(Query Editor) and Data tab in report designer window, if you look into my snapshot carefully.
Though I think they're equal, I'd use BLANK() when I comparing/counting blank values and use LEN to compare text type(Returns the number of characters in a text string) to make my DAX more comprehensible.
- Anonymous4 years agoNot applicable
I had a problem, that if I used BLANK() statement with int column, it filtered BLANK() and 0s as well.
instead: table[column] = BLANK()
use: LEN(table[column]) <> 0
SOLVED my problem