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.
I have a very simple DAX script written, however, DAX engine seems to ignore 'ORDER BY' (as per screenshot below). Any idea how to force DAX engine to take ORDER BY into consideration?
EVALUATE
SUMMARIZECOLUMNS(
'Table'[Year], 'Table'[Color],
FILTER('Table', 'Table'[Year] = "2000"),
"Sales Total", SUM('Table'[Sales]))
ORDER BY
"Sales Total" DESC
Solved! Go to Solution.
It needs to know how to handle the other columns. You should also avoid putting FILTER over an entire table, just use the VALUES in the column(s) you want to filter.
EVALUATE
SUMMARIZECOLUMNS (
'Table'[Year],
'Table'[Color],
FILTER ( VALUES ( 'Table'[Year] ), 'Table'[Year] = 2000 ),
"Sales Total", SUM ( 'Table'[Sales] )
)
ORDER BY
"Sales Total" DESC,
'Table'[Color],
'Table'[Year]
No, you don't need to include them all every time.
https://docs.microsoft.com/en-us/dax/orderby-statement-dax
It needs to know how to handle the other columns. You should also avoid putting FILTER over an entire table, just use the VALUES in the column(s) you want to filter.
EVALUATE
SUMMARIZECOLUMNS (
'Table'[Year],
'Table'[Color],
FILTER ( VALUES ( 'Table'[Year] ), 'Table'[Year] = 2000 ),
"Sales Total", SUM ( 'Table'[Sales] )
)
ORDER BY
"Sales Total" DESC,
'Table'[Color],
'Table'[Year]
Nice example. Does it mean that for every "ORDER BY" clause, we have to explicitly mention all columns in that table?