Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Solved! Go to Solution.
Hey @v_mark ,
a calculated column and a measure are 2 different concepts. You cannot always convert one to another, otherwise there would not be a reason to have both.
In your case you create a value by each row. If you do that as a measure you lose abilities that a calculated column has, like filtering by that value.
So the real question is what exactly do you want to do?
Otherwise you can easily transform that into a measure, I'm just not sure if you can use it then:
Task Bucket =
SWITCH(
TRUE(),
MAX(Task[Aged]) <= 1, "<24hrs",
MAX(Task[Aged]) <= 3, "<72hrs",
MAX(Task[Aged]) >= 3, ">72hrs"
)
Hi @v_mark ,
First, please make sure the field Task[Aged] will be put on your visual. Then you can create the measure as below to replace the original caculated column [Task Bucket]:
Measure =
IF (
SELECTEDVALUE ( Task[Aged] ) <= 1,
"<24hrs",
IF ( SELECTEDVALUE ( Task[Aged] ) <= 3, "<72hrs", ">72hrs" )
)
Best Regards
Hi @v_mark ,
First, please make sure the field Task[Aged] will be put on your visual. Then you can create the measure as below to replace the original caculated column [Task Bucket]:
Measure =
IF (
SELECTEDVALUE ( Task[Aged] ) <= 1,
"<24hrs",
IF ( SELECTEDVALUE ( Task[Aged] ) <= 3, "<72hrs", ">72hrs" )
)
Best Regards
Hey @v_mark ,
a calculated column and a measure are 2 different concepts. You cannot always convert one to another, otherwise there would not be a reason to have both.
In your case you create a value by each row. If you do that as a measure you lose abilities that a calculated column has, like filtering by that value.
So the real question is what exactly do you want to do?
Otherwise you can easily transform that into a measure, I'm just not sure if you can use it then:
Task Bucket =
SWITCH(
TRUE(),
MAX(Task[Aged]) <= 1, "<24hrs",
MAX(Task[Aged]) <= 3, "<72hrs",
MAX(Task[Aged]) >= 3, ">72hrs"
)
Task Bucket =
SWITCH(
TRUE(),
MAX( Task[Aged] ) <= 1, "<24hrs",
MAX( Task[Aged] ) <= 3, "<72hrs",
">72hrs"
)
Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension! |
DAX is simple, but NOT EASY! |
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
114 | |
101 | |
78 | |
75 | |
49 |
User | Count |
---|---|
145 | |
108 | |
107 | |
89 | |
61 |