|Grouping Transactions by Age of Customers in DAX|
|Written by Marco Russo|
|Thursday, 25 April 2013 21:52|
Grouping transactions by customers' age requires a computation made row by row at transaction level. DAX offers an elegant solution using calculated columns, which is described in this article.
This scenario would be easier to implement if you want to consider the current age of Customer for any transaction she made in the past. However, if you have a transactions history that spans over several years, a better analysis is performed by considering the age of the customer at the moment of every transaction. With a large volume of data, in a star schema this requires the creation of a separate dimension just for the age of the customer, adding a column in the fact table that persists that age. This result in an expensive cost also for Analysis Services Multidimensional, because it increases cube's dimensionality.Read more...
Latest Author Articles
- LASTDATE vs. MAX? CALCULATETABLE vs. FILTER? It depends! #dax #powerpivot #tabular
- Last Process Date in SSAS Tabular
- Natural and Unnatural Hierarchies in #powerpivot and #tabular
- Natural Hierarchies in Power Pivot and Tabular
- Using Added Columns in #DAX Queries