Pre-emotively speaking i'm sensing there will be confusion between calculated columns and the custom column you can insert in the query layer. Might be a good idea to contemplate merging these two as just adding a "new column" either from the report view or the query view. realise that the underlying language is M and the calculated columns language so it isn't an easy decision. I would pick M only due to the big scripting component behind the scenes of Query. Would love to see what others think of this.
3 Comments
- I'm equally confused about the two, not sure what are the pros and cons of using them and when ...
- Interesting - I've found one use for the calculated columns. If I have an indicator column "Valid", with values "Y" and "N" - I usually want to sort by "Y" first. If I create "Valid_Sort" as DAX custom query-layer column for this, and then try to sort "Valid" by it, I get a "Sort By Another Column Error" due to dependencies. However, if I create "Valid_Sort" as a calculated column in the data layer (which is quite a bit more of a hassle, it must be said), I don't get the error and am able to sort "Valid" by "Valid Sort".
- Status added:Needs Votes
