Meaure counting 0 as blank?

[Clint]

Running into an issue filtering a measure that sums up values in one colume where the matching value in another column (same table) is not null or blank. Per the embedded image, the value for the sum of PBD should be 885 but instead I get 826. This seems to be because there are two values in the AB column that are 0 are being included in the filter of <>blank. There is one blank AB cell where the matching PBD value shouldn't be counted. the rest of the PBD values should be summed to get to the value of 885. Thoughts?

The measure I am using is:

Planned Burn total =

CALCULATE(SUM('Burndowns2'[PBD]),

FILTER('Burndowns2',[AB]<>BLANK())

)

 

[FrankAT · Accepted solution]

Hi @Clint 

use the following measure with strictly equal sign ==

See: https://dax.guide/op/strictly-equal-to/#)

Sum of PBD = 
CALCULATE(
    SUM('Table'[PBD]),
    'Table'[AB] <> BLANK() || 'Table'[AB] == 0
)

With kind regards from the town where the legend of the 'Pied Piper of Hamelin' is at home
FrankAT (Proud to be a Datanaut)

[Clint]

Thank you Frank.  This looks like it is working correctly.  What is the logic behind the strictly == 0 in terms of not being recognized as "not blank" by the original measure?

[FrankAT]

Hi @Clint 

take a look at the following link: https://dax.guide/op/strictly-equal-to/#

With kind regards from the town where the legend of the 'Pied Piper of Hamelin' is at home
FrankAT (Proud to be a Datanaut)