DAX using SWITCH and SELECTEDVALUE for an output based on a slicer selection










1














I have a column that shows number of hours aging ("AgingHours") for "Orders". I want to create another column called "Aged" that will = 1 if the "AgingHours" value is greater than the selected value in the slicer, otherwise 0. The user is able to select either "1 Hr", "2 Hrs", or "3 Hrs" from the slicer.



For example:



Created slicer called AgingDate[HourDay]. User selects "2 Hrs" from the slicer (which would mean, anything in the "AgingHours" column that is >= 2 would output a 1 in the "Aged" column. The output in the aged column below would be:



Order AgingHours Aged
A 1 0
B 2 1


I tried making a calculated column utilizing an IF statement based on the selection, but every value is showing 0.



Aged = 
SWITCH (
SELECTEDVALUE( AgingDate[HourDay] ),
"1 Hr", IF ( [AgingHours] >= 1, 1, 0 ),
"2 Hrs", IF ( [AgingHours] >= 2, 1, 0 ),
"3 Hrs", IF ( [AgingHours] >= 3, 1, 0 ),
0
)









share|improve this question





















  • Is there a specific reason you need it to be a column? How are you going to use the Aged value in your report?
    – Joe
    Nov 12 at 19:28










  • I am tying that to a synoptic panel. So for the panel that represents order B, it will be colored Red if the "Aged" value is > 0. Then there are three other conditions/colors that come from other tables.
    – oilers128
    Nov 12 at 19:41






  • 1




    A calculated column cannot respond to slicers. I think you want a measure.
    – Alexis Olson
    Nov 12 at 20:14















1














I have a column that shows number of hours aging ("AgingHours") for "Orders". I want to create another column called "Aged" that will = 1 if the "AgingHours" value is greater than the selected value in the slicer, otherwise 0. The user is able to select either "1 Hr", "2 Hrs", or "3 Hrs" from the slicer.



For example:



Created slicer called AgingDate[HourDay]. User selects "2 Hrs" from the slicer (which would mean, anything in the "AgingHours" column that is >= 2 would output a 1 in the "Aged" column. The output in the aged column below would be:



Order AgingHours Aged
A 1 0
B 2 1


I tried making a calculated column utilizing an IF statement based on the selection, but every value is showing 0.



Aged = 
SWITCH (
SELECTEDVALUE( AgingDate[HourDay] ),
"1 Hr", IF ( [AgingHours] >= 1, 1, 0 ),
"2 Hrs", IF ( [AgingHours] >= 2, 1, 0 ),
"3 Hrs", IF ( [AgingHours] >= 3, 1, 0 ),
0
)









share|improve this question





















  • Is there a specific reason you need it to be a column? How are you going to use the Aged value in your report?
    – Joe
    Nov 12 at 19:28










  • I am tying that to a synoptic panel. So for the panel that represents order B, it will be colored Red if the "Aged" value is > 0. Then there are three other conditions/colors that come from other tables.
    – oilers128
    Nov 12 at 19:41






  • 1




    A calculated column cannot respond to slicers. I think you want a measure.
    – Alexis Olson
    Nov 12 at 20:14













1












1








1







I have a column that shows number of hours aging ("AgingHours") for "Orders". I want to create another column called "Aged" that will = 1 if the "AgingHours" value is greater than the selected value in the slicer, otherwise 0. The user is able to select either "1 Hr", "2 Hrs", or "3 Hrs" from the slicer.



For example:



Created slicer called AgingDate[HourDay]. User selects "2 Hrs" from the slicer (which would mean, anything in the "AgingHours" column that is >= 2 would output a 1 in the "Aged" column. The output in the aged column below would be:



Order AgingHours Aged
A 1 0
B 2 1


I tried making a calculated column utilizing an IF statement based on the selection, but every value is showing 0.



Aged = 
SWITCH (
SELECTEDVALUE( AgingDate[HourDay] ),
"1 Hr", IF ( [AgingHours] >= 1, 1, 0 ),
"2 Hrs", IF ( [AgingHours] >= 2, 1, 0 ),
"3 Hrs", IF ( [AgingHours] >= 3, 1, 0 ),
0
)









share|improve this question













I have a column that shows number of hours aging ("AgingHours") for "Orders". I want to create another column called "Aged" that will = 1 if the "AgingHours" value is greater than the selected value in the slicer, otherwise 0. The user is able to select either "1 Hr", "2 Hrs", or "3 Hrs" from the slicer.



For example:



Created slicer called AgingDate[HourDay]. User selects "2 Hrs" from the slicer (which would mean, anything in the "AgingHours" column that is >= 2 would output a 1 in the "Aged" column. The output in the aged column below would be:



Order AgingHours Aged
A 1 0
B 2 1


I tried making a calculated column utilizing an IF statement based on the selection, but every value is showing 0.



Aged = 
SWITCH (
SELECTEDVALUE( AgingDate[HourDay] ),
"1 Hr", IF ( [AgingHours] >= 1, 1, 0 ),
"2 Hrs", IF ( [AgingHours] >= 2, 1, 0 ),
"3 Hrs", IF ( [AgingHours] >= 3, 1, 0 ),
0
)






powerbi dax






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 12 at 19:22









oilers128

123




123











  • Is there a specific reason you need it to be a column? How are you going to use the Aged value in your report?
    – Joe
    Nov 12 at 19:28










  • I am tying that to a synoptic panel. So for the panel that represents order B, it will be colored Red if the "Aged" value is > 0. Then there are three other conditions/colors that come from other tables.
    – oilers128
    Nov 12 at 19:41






  • 1




    A calculated column cannot respond to slicers. I think you want a measure.
    – Alexis Olson
    Nov 12 at 20:14
















  • Is there a specific reason you need it to be a column? How are you going to use the Aged value in your report?
    – Joe
    Nov 12 at 19:28










  • I am tying that to a synoptic panel. So for the panel that represents order B, it will be colored Red if the "Aged" value is > 0. Then there are three other conditions/colors that come from other tables.
    – oilers128
    Nov 12 at 19:41






  • 1




    A calculated column cannot respond to slicers. I think you want a measure.
    – Alexis Olson
    Nov 12 at 20:14















Is there a specific reason you need it to be a column? How are you going to use the Aged value in your report?
– Joe
Nov 12 at 19:28




Is there a specific reason you need it to be a column? How are you going to use the Aged value in your report?
– Joe
Nov 12 at 19:28












I am tying that to a synoptic panel. So for the panel that represents order B, it will be colored Red if the "Aged" value is > 0. Then there are three other conditions/colors that come from other tables.
– oilers128
Nov 12 at 19:41




I am tying that to a synoptic panel. So for the panel that represents order B, it will be colored Red if the "Aged" value is > 0. Then there are three other conditions/colors that come from other tables.
– oilers128
Nov 12 at 19:41




1




1




A calculated column cannot respond to slicers. I think you want a measure.
– Alexis Olson
Nov 12 at 20:14




A calculated column cannot respond to slicers. I think you want a measure.
– Alexis Olson
Nov 12 at 20:14












1 Answer
1






active

oldest

votes


















3














Calculated columns are only evaluated once when the data is loaded. Therefore, they cannot respond to any slicers or filtering on your report page.



In particular, SELECTEDVALUE( AgingDate[HourDay] ) is returning a blank value (since it doesn't know what single value you have selected), which means your SWITCH is taking the else value of 0.



If you use the same code as a measure, it looks like it should work OK as long as you use the table name as well when you refer to [AgingHours].






share|improve this answer




















  • Makes prefect sense. Measure has it working as expected...Thanks!
    – oilers128
    Nov 12 at 20:26










Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53268765%2fdax-using-switch-and-selectedvalue-for-an-output-based-on-a-slicer-selection%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














Calculated columns are only evaluated once when the data is loaded. Therefore, they cannot respond to any slicers or filtering on your report page.



In particular, SELECTEDVALUE( AgingDate[HourDay] ) is returning a blank value (since it doesn't know what single value you have selected), which means your SWITCH is taking the else value of 0.



If you use the same code as a measure, it looks like it should work OK as long as you use the table name as well when you refer to [AgingHours].






share|improve this answer




















  • Makes prefect sense. Measure has it working as expected...Thanks!
    – oilers128
    Nov 12 at 20:26















3














Calculated columns are only evaluated once when the data is loaded. Therefore, they cannot respond to any slicers or filtering on your report page.



In particular, SELECTEDVALUE( AgingDate[HourDay] ) is returning a blank value (since it doesn't know what single value you have selected), which means your SWITCH is taking the else value of 0.



If you use the same code as a measure, it looks like it should work OK as long as you use the table name as well when you refer to [AgingHours].






share|improve this answer




















  • Makes prefect sense. Measure has it working as expected...Thanks!
    – oilers128
    Nov 12 at 20:26













3












3








3






Calculated columns are only evaluated once when the data is loaded. Therefore, they cannot respond to any slicers or filtering on your report page.



In particular, SELECTEDVALUE( AgingDate[HourDay] ) is returning a blank value (since it doesn't know what single value you have selected), which means your SWITCH is taking the else value of 0.



If you use the same code as a measure, it looks like it should work OK as long as you use the table name as well when you refer to [AgingHours].






share|improve this answer












Calculated columns are only evaluated once when the data is loaded. Therefore, they cannot respond to any slicers or filtering on your report page.



In particular, SELECTEDVALUE( AgingDate[HourDay] ) is returning a blank value (since it doesn't know what single value you have selected), which means your SWITCH is taking the else value of 0.



If you use the same code as a measure, it looks like it should work OK as long as you use the table name as well when you refer to [AgingHours].







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 12 at 20:21









Alexis Olson

12.4k21633




12.4k21633











  • Makes prefect sense. Measure has it working as expected...Thanks!
    – oilers128
    Nov 12 at 20:26
















  • Makes prefect sense. Measure has it working as expected...Thanks!
    – oilers128
    Nov 12 at 20:26















Makes prefect sense. Measure has it working as expected...Thanks!
– oilers128
Nov 12 at 20:26




Makes prefect sense. Measure has it working as expected...Thanks!
– oilers128
Nov 12 at 20:26

















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53268765%2fdax-using-switch-and-selectedvalue-for-an-output-based-on-a-slicer-selection%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Top Tejano songwriter Luis Silva dead of heart attack at 64

政党

天津地下鉄3号線