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 August 31st. Request your voucher.
Solved! Go to Solution.
Hi @Allisond
It's abit complicated to understand but looking at your SWITCH, the order of the logic needs changing. If ValidRow is True then the 2nd line (ValidRow && ThirtyDWt) will never be evaluated
Try this
Return
SWITCH(
TRUE(),
ValidRow && ThirtyDWt = BLANK(), ThirtyMin1Wt,
ValidRow, ThirtyDWt,
BLANK()
)
Regards
Phil
Proud to be a Super User!
Hi @Allisond
It's abit complicated to understand but looking at your SWITCH, the order of the logic needs changing. If ValidRow is True then the 2nd line (ValidRow && ThirtyDWt) will never be evaluated
Try this
Return
SWITCH(
TRUE(),
ValidRow && ThirtyDWt = BLANK(), ThirtyMin1Wt,
ValidRow, ThirtyDWt,
BLANK()
)
Regards
Phil
Proud to be a Super User!
Could you please provide a sample dataset or PBIX file? And a depiction of what you are trying to calculate
Proud to be a Super User!
Paul on Linkedin.
Ah! So I have a number of these parameters. I will try to plug those in this am and use the original last and give it a try this am and get back. Thank you!
OK no worries. Yes, the order of the lines is important.
Regards
Phil
Proud to be a Super User!
I was not leveraging the logic correctly thinking about the "true" and how if false then moves to the next. Adjusted my statements to
Valid Row && ThirtyDWt <> BLANK(), ThirtyDWt,
Valid Row && ThirtyDMin1Wt <> BLANK(), ThirtyDMin1Wt,
Etc.
And this seemed to take care of it. Thank you for your help in getting me to think this through.
Hi @Allisond
If my answers helped to solve your problem please mark my answer(s) as the solution.
regards
Phil
Proud to be a Super User!