The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
I thought the key purpose of Divide was to protect against numerator errors and zero division.
On my current report I have blanks (BLANK()) as my Numerator and when this is the case Divide returns BLANK() instead of returning my alternate result 0, why?
DivBlank:=DIVIDE(BLANK(), 10 ,0)
#RETURNS BLANK()
Is there a way to fix it without putting conditionals in the numerator and denominator to error check for blanks?
This is my current solution, but wish it wasn't.
=IF(AND(ISBLANK([MyTrue]),[MyFalse]>0),0,DIVIDE([MyTrue],[myTrue]+[MyFalse],0))
Solved! Go to Solution.
Hi @Anonymous
You may add +0 in your formula to avoid using IF condition. Measure =
DIVIDE([MyTrue]+0,[myTrue]+[MyFalse])
For example:
Regards,
Cherie
Hi @Anonymous
You may add +0 in your formula to avoid using IF condition. Measure =
DIVIDE([MyTrue]+0,[myTrue]+[MyFalse])
For example:
Regards,
Cherie
Hi @Anonymous
Glad to hear the reply is helpful, please accept the reply as solution, that way, other community members will easily find the solution when they get same issue.
Regards,
Cherie
These two articles attempt at an explanation:
https://docs.microsoft.com/en-us/dax/blank-function-dax
Basically, blanks are not nulls and are handled differently with DAX compared to Excel.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
112 | |
80 | |
75 | |
52 | |
50 |
User | Count |
---|---|
132 | |
124 | |
78 | |
64 | |
61 |