The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
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?
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
109 | |
76 | |
65 | |
52 | |
51 |
User | Count |
---|---|
128 | |
117 | |
78 | |
65 | |
63 |