Calculated Columns in DAX, why?

[Burningsuit]

Can anyone give a good reason (other than backwards compatability) for using calculated columns in DAX?

As I see it, I can create columns in Query (Which get compressed into the data model) for everything I need, rather than creating calculated columns in DAX (which may not get compressed, hence inflating the data model). For everything else there's Measures. So I'm struggling to find a use case for DAX Column Calculations, or have I missed something?

regards

Stuart

[Greg_Deckler]

There are a number of reasons but probably primarily ease of use. There are certain things that are just easier to do in DAX rather than in "M" code. A good example of this is dealing with dates and times. For certain things it is 1 line of DAX versus multiple complex lines of M code. In addition, DAX is very Excel formula like. M is a complex, functional programming language and the Query Editor does not provide easy access to perhaps 50-60% or more of what M is capable of. And not everyone is a developer out there.

Also remember that DAX is part of SQL Server Analysis Services Tabular. So it's application goes beyond Power BI. Power BI just happens to use SSAS Tabular under the hood so DAX kind of comes along for the ride.