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!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hello,
There's a bug with using the ORDERBY() parameter with a column sorted by another column. To recreate this issue, I created a Date Table with a column for the month name, and a measure called Number 1, and a visual calculation called test. [Month] in the Date table is sorted by [Month Sort].
Date = ADDCOLUMNS(CALENDARAUTO(),
"MonthSort", FORMAT([Date], "yyyymm"),
"Month", FORMAT([Date], "mmm yyyy"))Number 1 = 1test = RUNNINGSUM([Number 1], ORDERBY([Month], ASC))
As seen in the screenshot, the [test] visual calculation is ordering by the literal [Month], rather than the underlying [Month Sort] column. If I use the [Month Sort] column instead of [Month], then it works perfectly fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.