Pq is a specialized language, but so nice. It generates sql with Query Folding. And easy for someone to reproduce in sql etc. For power user maybe not for business user it’s probably just the right thing.
Powerquery is also a Microsoft proprietary language. The problem of change in cardinality is not specific to DAX. Saying so is misleading. Oh and validation... Have you heard of DAX studio? I'm not pro dax columns, but you are overselling your point
Great comments. Cardinality - Changing cardinality is a universal problem, but if this is done at another layer, you can insert a data check prior to the data moving to the Gold layer and stopping it. Impossible to stop a definition in DAX. It's calculated at the last possible step so it is not possible to test until after the refresh and impact. Validation - Again, this validation can only occur after users see the information if it is calculated in a DAX column. No room for data validation steps prior to users. I list all of these out because I do not know what combination of reasons to NOT use DAX Columns will finally resonate with the DAX Columns lovers out there.
