Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
Just a little background on the above table:
Project Name, Category Name, and Portfolio Name are from a table called 'Projects"
Actual, Committed are from a table called 'Expenses'
Projects is a one to many relationship with Expenses
In the above scenario, the project "cancer test project 5" has no related records in the Expenses table, so it is showing as blank, is there a way to show 0 instead
I have tried doing the following in the Projects table, but it gave unexpected results: Actual = IF(ISBLANK(SUMX(RELATEDTABLE('Expenses'), [Actual])) = FALSE(), SUMX(RELATEDTABLE('Expenses'), [Actual]), 0)
Solved! Go to Solution.
Hi, please try with this Dax Formula in a measure:
ActualM = IF ( CALCULATE ( SUM ( Expenses[Actual] ) ) = BLANK (), 0, CALCULATE ( SUM ( Expenses[Actual] ) ) )
Even easier would be to add zero to your Measure
Then you don't need an IF statement to check if the expression returns BLANK ( )
So if your SUMX Measure works get rid of the IF statement and just add " + 0 "at the end
same with if you use any other expression (something like this for example)
Measure = CALCULATE ( SUM (table[column] ), FILTER (... ) ) + 0
This will ensure you get a 0 when its blank!
Good Luck!
UPDATE: March 2020
New DAX COALESCE function - returns the first argument that is not blank!
If all arguments return blank then COALESCE returns blank as well!
So if you need a zero returned and not blank and your Measures don't address the blanks on their own
Add a zero as the last argument in case all Measures return blanks!
COALESCE ( [Measure1], [Measure2], 0 )
Smartest and best answer!!
I've had multiple connections and for some reason adding a zero made my pivot disconnect with everything else and eventually messing everything up... my logic is that when I added a fixed value which was not part of the datamodel and that's why my pivot disconnected from everything.
The solution (same same but different).... adding + [var] - [var]... and the var should have some value, eg be a base value.
I have a slightly diffrerent issue... I have data where i am trying to caluculate a daily average over a range of days. For spme of the items, they have data for every day in the range, but for others they do not... so for example, Buidling A has data for all 10 days of the period analyzed. The simple daily average for Building A is SUM(Values)/10 days. For Building B however, say it only has data for 5 of the days... to calculate the simple average for Buliding B over the entire 10 day range, I need to simply divide by 10 as well, but the results, after trying ~10 different methods, always divides by only the 5 days where Building B had data... how do I force the blank days to be counted as zeros?
Hi
First of all, dont use (values)/10 use DIVIDE(Values),10) or you could get a divide by zero error.
try:
My Measure :=
VAR Values =
SUM ( 'table name'[Column name] )
RETURN
COALESCE ( DIVIDE ( Values, 10 ), 0 )
This will avoid the possibility of divide by zero, which is good practice and give you a zero if there is no data
Do you have a copy of you DAX formula, by chance?
It sounds like you could do a count against the day column and use that as your denominator.
Could you not look up the first and last days in your sample and then use datediff to get your denominator?
Hello, this doesnt work at all with my Power Pivot both examples. The cells stay blank which then distrupts my growth calculation
Having to write a measure everytime you want to add a field (count, sum, etc) to a card is a poor solution. Not only do you have to create and mange the measures which provide virtually no value, but measures are a performance drain.
I know the measures wouldn't cause much of a drain, but if you have a report that is struggling for performance, the last thing you want is to be creating several extra measures.
Microsoft should fix this.
Wow, just add zero! Such a simple and elegant solution. Very nice! Thank you!
Doh! Your solution was so simplistic that I totally missed that option. That has saved me a lot of recoding and hair pulling. Thank you!
Oh wow, what an elegant solution. Wish I'd searched and found this first, before trying to figure out myself. Thanks!!
Check out the April 2025 Power BI update to learn about new features.
Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
User | Count |
---|---|
102 | |
68 | |
46 | |
37 | |
37 |