Solved: Re: Creating a Column - Model Efficiency/Storage/B...

nmasimore · ‎02-28-2022

Hello

I have a transaction table and a calendar table. The transaction table has a Datetime column, not a date column.... so I am creating a column in the transaction table called "Date" and it will contain strictly the date (no time).

In terms of model efficiency/data storage/best practice, should I create this column using PowerQuery or DAX?

Open-ended question: When is it better to create columns using Power Query? When is it better to create columns using DAX?

Syk · ‎02-28-2022

It's almost always better to create it in Power Query. You can read more about it here: https://www.sqlbi.com/articles/comparing-dax-calculated-columns-with-power-query-computed-columns/

View solution in original post

AllisonKennedy · ‎02-28-2022

@nmasimore , I agree with @Syk . If you can create it in Power Query (or even better at the data warehouse) then do so. I find that DAX is handy for creating calculated columns that require referencing multiple tables, but that shouldn't be a common requirement.

Please @mention me in your reply if you want a response.

Copying DAX from this post? Click here for a hack to quickly replace it with your own table names

Has this post solved your problem? Please Accept as Solution so that others can find it quickly and to let the community know your problem has been solved.
If you found this post helpful, please give Kudos C

I work as a Microsoft trainer and consultant, specialising in Power BI and Power Query.
www.excelwithallison.com