This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
An operation that could be done both with PowerQuery M and with DAX
Is it better to do it with PowerQuery M or No difference?
Solved! Go to Solution.
Hi @tlotfi
Power query is better for model data (clean, transform etc.) but DAX is better for calculations (specially for measures which don't take a lot of ram when you’re doing massive computations).
Good thread to go through.
https://community.powerbi.com/t5/Desktop/Dax-or-M-Language/td-p/136827
I would say that if it can be done in PowerQuery, that's where you should do it so that you don't slow down PowerBI after the data is loaded. For example, if you're creating another column, it's best to do that in PowerQuery as once it's done, it's done. If you do a calculated column in DAX, then everytime you apply a filter, cross-filter, or whatever, the calculated column get re-calculated.
I would say that if it can be done in PowerQuery, that's where you should do it so that you don't slow down PowerBI after the data is loaded. For example, if you're creating another column, it's best to do that in PowerQuery as once it's done, it's done. If you do a calculated column in DAX, then everytime you apply a filter, cross-filter, or whatever, the calculated column get re-calculated.
Hi @tlotfi
Power query is better for model data (clean, transform etc.) but DAX is better for calculations (specially for measures which don't take a lot of ram when you’re doing massive computations).
Good thread to go through.
https://community.powerbi.com/t5/Desktop/Dax-or-M-Language/td-p/136827
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 28 | |
| 23 | |
| 22 | |
| 16 | |
| 16 |
| User | Count |
|---|---|
| 61 | |
| 35 | |
| 28 | |
| 22 | |
| 22 |