Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I have a query that just broke unexpectedly recently after presumably a powerbi update. You can see the condition that broke in the below image:
= Table.AddColumn(chose2, "NextDate", each if [nd2] is null then null else if [nd2] >= 2 then [NextDate2] else [NextDate4], type date)
It seems that "if [nd2] is null" is causing an error to occur, instead of evaluating properly, when the input is null. This worked successfully previously.
Hi @moody31415
As tested with the last version, it works as well.
Could you show a simple example for analysis?
Best Regards
Maggie
Community Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.