The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
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.
User | Count |
---|---|
65 | |
61 | |
60 | |
53 | |
30 |
User | Count |
---|---|
180 | |
88 | |
71 | |
48 | |
46 |