Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
edhans
Super User
Super User

Why does NOT() prevent converting boolean to numerical values? DAX Mysteries

edhans_0-1601437980296.png

In the above image, I can convert the True/False in the [Value] column to a number by multiplying by 1. Great.

edhans_1-1601438033769.png

However, as shown above, if I wrap [Value] with NOT(), thus changing true to false and false to true, I can not convert it to a number by multiplying by 1. It stays as a true/false value.

Why is that? What am I missing?

 

 



Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

DAX is for Analysis. Power Query is for Data Modeling


Proud to be a Super User!

MCSA: BI Reporting
2 ACCEPTED SOLUTIONS
Anonymous
Not applicable

Hi @edhans 

I followed your steps and got the same result.

What I noticed is that the data type still remained "True/False" instead os changing to Whole number unlike for "Column".

pranit828_1-1601440074711.png

Changing it to Whole number serves the purpose.

pranit828_2-1601440113372.png

As to why it is behaving in such way still might be a question as it follows the similar construct as "Column".

This might have to do with how Power BI internally finalises the data type.

 

View solution in original post

Interesting @Anonymous - good catch on the data type. I also found out that if I used it as an operator and not as a function it works without having to change the data type.

edhans_0-1601464972477.png

And, of course, I hit this behavior inside of a measure where you cannot change the data type, nor could you deeper in a more detailed function even inside of a calculated column. But good thinking!



Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

DAX is for Analysis. Power Query is for Data Modeling


Proud to be a Super User!

MCSA: BI Reporting

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Hi @edhans 

I followed your steps and got the same result.

What I noticed is that the data type still remained "True/False" instead os changing to Whole number unlike for "Column".

pranit828_1-1601440074711.png

Changing it to Whole number serves the purpose.

pranit828_2-1601440113372.png

As to why it is behaving in such way still might be a question as it follows the similar construct as "Column".

This might have to do with how Power BI internally finalises the data type.

 

Interesting @Anonymous - good catch on the data type. I also found out that if I used it as an operator and not as a function it works without having to change the data type.

edhans_0-1601464972477.png

And, of course, I hit this behavior inside of a measure where you cannot change the data type, nor could you deeper in a more detailed function even inside of a calculated column. But good thinking!



Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

DAX is for Analysis. Power Query is for Data Modeling


Proud to be a Super User!

MCSA: BI Reporting

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.