I was helping a friend out recently with an interesting problem. It all started with a SUM( ) that wasn’t behaving. It quickly became a SUMX( ) problem but evolved into a DAX Studio/Query problem. Let me explain.

## The Root Problem – Same Store Sales

Many retail businesses open and close stores throughout any given year. This creates a problem because it is difficult to determine if business growth is vertical (increased sales within existing stores) or horizontal (expansion of the store base). It is common to do analysis on “same store sales” where you only include stores that had sales for the entire period this year and also last year. There are quite a few posts already on this topic on PowerPivotPro.com, but this is a good opportunity for me to talk about SUMX and also DAX as a query language. I have reconstructed the scenario with some test data. You can download the workbook here if you want to take a look.

I started off with some base measures as follows:

A. Total Sales:=SUM(Sales[Extended Amount]) B. Total Sales LY:=CALCULATE([Total Sales], SAMEPERIODLASTYEAR(Calendar[Date]))

There are a few different ways to work out sales last year, but I have used SAMEPERIODLASTYEAR above and this works just fine in this instance.

When placed in a Pivot Table, these measures look like this. I only want to analyse sales where there is a value for This Year (TY) AND Last Year (LY) for each particular store, and this table makes it easy to visualise when that occurs.

### Pivot Table 1

Notice how my test data is set up so there are some stores opening and closing at different times of the year in 2014 and 2015. **Creating good test data and setting up a pivot table that reflects what will happen in real life is essential if you want to eliminate rework and get the DAX right the first time.**

Let’s start with a simplistic Same Store Sales solution **that only works in some circumstances.**

C. Same Store Sales TY Simplistic:=CALCULATE([Total Sales], FILTER(Stores, [Total Sales] > 0 && [Total Sales LY] > 0 ) ) D. Same Store Sales LY Simplistic:=CALCULATE([Total Sales LY], FILTER(Stores, [Total Sales] > 0 && [Total Sales LY]> 0 ) )

Both of these above simplistic Same Store formulae will work in very limited scenarios **where the Pivot Table provides an initial filter context for the time period**. Note in Pivot Table 2 below how “Same Store Sales TY Simplistic” is showing the correct values for each month in 2015 (shown as 1 in the Pivot below). If you look Pivot Table 1 above and compare it with Pivot Table 2 below, you can see Store 2 opened in month 4 2014 and closed in month 10 2015, so Same Store sales in any given month (shown in box 1 below) are all correct.

### Pivot Table 2

The problem is that the 2015 total (shown as 2 above) is not correct. The sub total for Store 2 2015 is showing the value $2,678 but if you add up all the values in the box 1 above, the numbers only add up to $1,977. This is a common problem that can normally be solved by using SUMX. (Note: there are lots of other posts about SUMX at PowerPivotPro.com if you are interested). This “doesn’t add up” problem is not occurring in the Grand Total for rows (shown as 3 above) because the FILTER function in my DAX formula is iterating across the Stores table and hence each store is being treated as an independent entity for FILTER evaluation purposes. The cause of the problem (shown as 2 not adding up correctly) can be a little hard to understand unless you truly understand how Power Pivot works under the hood.

## How the Power Pivot Engine Works.

Power Pivot first of all takes the initial filter context from the Pivot Table and filters the underlying tables so that only the relevant rows are presented to the formula engine. Let’s take the cell highlighted as 4 above. The initial filter context from the Pivot Table has filters on Stores[Store]=”Store 4”, Calendar[Year]=2015 and Calendar[Month]=8. So the only rows in my sales table that are available to the pivot table for the calculation of this cell are the rows that match this filter context. Once the underlying tables are filtered to reflect this filter context, then and only then does the formula engine kick in and calculate the answer to my DAX expression:

C. Same Store Sales TY Simplistic:=CALCULATE([Total Sales], FILTER(Stores, [Total Sales] >0 && [Total Sales LY] >0 ) )

Given that the cell shown as 4 above is filtered for the month of August 2015, the part of the formula **[Total Sales] > 0 && [Total Sales LY] > 0 **will successfully work out if the current month needs to be included. If there are sales for “this month, this year” and also the “same month last year” for this store, then the sales for TY will be included and returned to this cell in the Pivot Table. But the problem with the sub total row (shown as 2 above) is that there is no such filtering on months. So the initial filter context coming from this sub total in the above Pivot Table is simply Stores[Store]=”Store 2” and Calendar[Year]= 2015. **There is no filter on month.** So when the part of the formula **[Total Sales] > 0 && [Total Sales LY] > 0 **is evaluated, it is evaluated across the entire year instead of a single month. As long as there was a single sale in the year 2015 and also a single sale in the year 2014 for an individual store, the entire year’s sales for that store will be included in the sub total (shown 2 above). You can see this total $2,678 in Pivot Table 1 – it is the total for all month sales for Store 2 (you can check it against the total shown in Pivot Table 1 to confirm).

So in short, the initial filter context coming from the rows in the Pivot Table is ensuring the Same Stores sales by month is working at the row level. As soon as you remove the initial filter context on month by removing the months from the Pivot Table (or like is happening at the sub total level), this formula is not going to work. Whenever this problem happens, my first instinct is to jump to SUMX. SUMX is an iterator and hence **SUMX can simulate the existence of rows in a Pivot Table**. Take the following formula.

E. Simple SUMX:= SUMX(Calendar, IF( [Total Sales] > 0 && [Total Sales LY] >0,[Total Sales] ) )

Now this formula (E) iterates over the Calendar table and checks to see if there are sales this year as well as last year (at a day level of granularity because my Calendar table has day level data). If there are sales in both years, then the sales are included in the resulting total. But this creates a new problem that didn’t exist in formula D. The new problem is there is no longer an iterator working on the Stores table. **Without the FILTER( ) on the Stores table (or maybe another SUMX), the totals for All Stores will not add up correctly. ** In fact the same problem that occurred with “Months” will now occur with “Stores”. When the formula is at the sub total level, the sales for all stores will be included in the result.

So one way to solve this problem is to use a double iterator and **iterate over both the Stores table and also the Calendar table**. You can do it like this with a double SUMX

### F: Double Nested SUMX

..or a FILTER with SUMX.

### G: FILTER and a single SUMX.

But either way, this is not going to be very performant because they both have double iterators. So I asked around and Scott from TinyLizard.com suggested I check out SUMMARIZE. I have watched Alberto Ferrari’s Many to Many presentation often enough to know that SUMMARIZE was a likely contender. I can still hear Alberto saying ** ‘SUMMARIZE uses a single Vertipaq operation…’** and hence I know SUMMARIZE is going to be faster than using a double nested SUMX pattern.

## My journey to find the right DAX Query formula.

Anytime I start using DAX as a query language to solve a particular problem, I ALWAYS fire up DAX Studio. It is not that hard to use and it allows you to “see” the results of your formulae as you are writing them. I always write my exploratory DAX formulae from the inside out, building it up one piece at a time, and DAX Studio makes this process a snap. I did a quick refresher on SUMMARIZE at SQLBI.COM and I started out with this:

SUMMARIZE is a bit like GROUP BY in SQL and it creates the first 2 columns of the table in the image above summarised to the level specified.

If you read the article at the above SQLBI.COM link the clear advice is to use ADDCOLUMNS rather than SUMMARIZE when creating __new columns of data on the fly__, so that is what I did above. Once I executed this query (shown in the image above) I could ‘see’ that this was giving me what I needed (in the results window above).

The next step was to **filter out the columns that didn’t have sales for this year as well as last year**. So I wrapped the above Query inside a FILTER and got the results below

Now that I could “see” that my DAX Query was correctly returning a table of only the values that I needed, I then realised that I could easily swap out Calendar[Date] for another column in my Calendar table. This has the effect of making this table smaller (and hence presumably faster to execute) while still giving me the level of granularity I needed for my reporting (monthly in this instance). So I swapped out the [Date] column for the [YYMM] (year/month ID column). If you were doing Same Store sales by week, then you would need to use a WeekID column here instead.

The last step was to wrap this table inside a CALCULATE to get the final result.

### H: SUMMARIZE, ADDCOLUMNS and FILTER

I just repeated the process for [Total Sales LY].

Now the reason the above formula works and the original formula (C) doesn’t work is because **the above formula is not relying on the initial filter context from the Pivot Table to work.** The SUMMARIZE potion of the query creates a summarised table containing all the possible month-year combinations and the Store ID. Then the ADDCOLUMNS portion of the formula kicks in. ADDCOLUMNS has a row context as it works through the SUMMARIZE table, and this row context is converted to a filter context by the implicit CALCULATE function that is part of the [Total Sales] and [Total Sales LY] measures. The new columns TY and LY therefore get populated with the total sales for that store for that month in the row/filter context. The FILTER portion of the formula then filters out the periods that should not be included (those that don’t have sales in both years). Because it is operating over the table produced on the fly by this query, it works regardless if the Pivot Table has a filter on Months and/or Stores or not.

## So why is the Query approach better?

There are 3 formulae that I have discussed here that all work for Same Store Sales:

- F: Nested SUMX
- G: SUMX with FILTER
- H: SUMMARIZE with ADDCOLUMNS and FILTER

The nested SUMX is going be the slowest to execute. This formula has a SUMX nested inside a second SUMX. SUMX is an iterator and hence it will step through every row in the table 1 row at a time. And given the SUMX are nested, there is a multiplicative effect. If there are 500 stores and 730 days, then there will be 500 x 730 iterations. And then there is the filtering and calculation on top of that and remember this is repeated for EVERY CELL in the pivot.

The SUMX and FILTER is a bit better, but FILTER is also an iterator. The benefit of this second formula is that at least they are not nested. So FILTER is executed first (730 iterations) and SUMX then kicks in, so there are 500 + 730 iterations.

Finally the SUMMARIZE with ADDCOLUMNS and FILTER is going to be the most performant. SUMMARIZE leverages the power of the Vertipaq Storage engine to rapidly create a table on the fly. ADDCOLUMNS quickly creates the required sub totals so that this table is as small as possible but contains all the information required for the calculation. By the time FILTER is asked to do an iteration, most of the hard work has already been done by the storage engine and hence FILTER only has to work across the smallest possible table of data. The result is a very efficient and performant calculation.

Matt Allington is the Author of the soon to be released book Learn to Write DAX, and provides Self Service BI Consulting and training in Australia.

That’s a very fine laid out blog post Matt. I particularly like the way that you tune in on the right solution step by step by using Dax Studio. That makes it a lot easier both to follow and understand the process and not the least the logic behind the final solution.

I believe that Dax Sudio is a very much overlooked tool for learning DAX and debugging DAX formulas. That especially goes for people who are working exclusively inside Excel (as opposed to working with SSAS tabular and it’s client tools).

Very fine blog post.

Thanks for your comments and support. I agree with your comments about DAX studio, and also about writing DAX. I think it is good for everyone learning DAX to realise that there is a process to get the right answer, and there are very few brainiacs that can just pull the right answer out the first time.

Does anyone know a source for learning a little more about how to utilize the DAX Studio? This is about the best blog I’ve found with an example of someone using the software and the documentation at http://daxstudio.codeplex.com/documentation really wasn’t very helpful. Ferrari has a good video on optimizing DAX Queries, but it is using SQL Profiler and SSMS for the analysis which is still way over my excel brain’s comprehension. https://www.youtube.com/watch?v=1v0xUX8Bve8

I think the issue with the lack of content and documentation is that DAX studio was built for SQL Server pros that are using Power Pivot. These people already know how to use the profiling tools (and query language) and hence they don’t need the documentation. For the rest of use mere mortal Excel users, we have to hunt, scrounge and teach ourselves. This sounds like a good thing to add to the list of potential blog posts.

I know there is a post at TinyLizard http://tinylizard.com/dax-studio/

Thanks for sharing your path to DAX efficiency.

Hello, I have the following problem:

My table has Prices, Products, Dates and Stores. Something like a price history.

What I need is to find latest price for every store (provided the price falls into given filter Date context) and return the average for such latest prices.

LASTDATE and LASTNONBLANK don´t seem to work because without Store context they always return latest available date and Stores where I dont have price for that date are skipped.

Thank you

Martin

Hi Martin

It is difficult to give advice without seeing the data model. I suggest you prepare a sample workbook that has data in the structure you are using, and then post the question along with the sample workbook on http://powerpivotforum.com.au

Hi Matt, I did as you said, thank you.

Hi Matt, I’ll try to give it shot to put in practice what I have learned from you, the italians and Rob.

Hi Martin, because you need the latest price for every store and the average price for all stores, the following DAX query computes only those values which you can see in a pivot table with Store on Rows, AveragePrice on Values (LastPrice for every Store) and the AveragePrice for all Stores in the Total row. I have not taken into account the Products column given that you don’t need average prices by product. You can test this DAX query on DAX Studio and use it to create the measure “AveragePrice”. If you use a Slicer to filter the pivot table by Dates it will show you the last price for every store and the average of all stores that had sales on that date. If you don’t filter by dates you will have the last date and average price of the last date that each store had sales. Hope this is what you requested.

EVALUATE

ROW(“AveragePrice”,

AVERAGEX(

ADDCOLUMNS(

SUMMARIZE(

Data,

Data[Store]

),

“LastDate”,LASTDATE(Data[Dates]),

“LastPrice”,LASTNONBLANK(Data[Prices],1)),

[LastPrice]))

I followed your pattern on Same Store Sales to create a model that compares CY and LY employee hours only for instances where CY & LY are both 0 for a given month for data that is already aggregated at a month level. When using the ADDCOLUMNS and SUMMARIZE pattern, I got an error that I doubt you would encounter with store sales. In my employee hours data, sometimes an employee’s hours will drop to zero in the midst of non-zero hours in the months before and after (the employee goes on leave or something similar). I get the non-contiguous dates error in the calculation of the LY measure. I believe this is due to non-contiguous dates being passed back to the CALCULATE function by the filter as the date for the zero-month data is abruptly dropped out. I wonder if you get the same error if you happen to change a the sales from one store to zero in a period where there are sales before and after (i.e. all of the sudden, sales just drop to zero). I’ve been struggling to find a workaround. I have not tried your other SUMX patterns presented here, but wonder if any simple solutions come to mind.

Robert

Hard to help you without the entire picture. I am only aware of non-contiguous issues when using inbuilt time intelligence functions such as TOTALYTD. If this is the issue, then switching to a GFITW solution (search on Rob’s site) should fix the problem. Otherwise feel free to create a sample workbook and post at http://powerpivotforum.com.au to see some specific help.

Thanks for sharing the insight Matt. I am however facing a problem while trying to calculate the same store growth rate (SSG) i.e. % of increase (or decrease) of current year sales over last year.

If i use the nested SumX method the table is filtered properly i.e. only those rows are visible where there was sales in current year as well as previous year. However the calculation in to row total is summation of individual SSG for months rather than the difference between the like to like sales of the 2 year.

If i use AddColumn & Summarize method then the row total problem is solved, however the data in SSG column also includes rows (i.e months) which did not have sales (either in current year or previous year or both years). The calculated value is -1 (or -100%).

How to solve this issue to show appropriate %age difference between the 2 columns created above (

Hi Amit

How about you create a sample workbook showing what is currently happening and what you want at http://powerpivotforum.com.au

Hi Matt,

Thanks for the suggestion. Have uploaded a sample file on the http://powerpivotforum.com.au/viewtopic.php?f=6&t=270

Hi

Just came across this article. I haven’t tried yet, but I think it will fit very well for a particular need I have. Regarding DAX studio, I tried to install it but it requires to pieces of software. It offers to download them, but then it fails (probably the links are old). Even if I install the software required (SQL Server 2016 ADOMD.NET and SQL Servver 2012 Analysis Management Objects, it still indicates that SQL Server 2012 Analysis Management objects is missing.

If somebody knows how to go around that, it will be greatly appreciated.

David

Have you tried the support at daxstudion.codeplex.com?

Hi Matt

Thanks, yes I reached out to them and the versions for the program needs to be the 2016 version. Downloaded it manually and then was able to install DAX Studio.

Regards

David

Hi Matt,

Thanks for this blog, really easy to follow and the exact issue I had last week (if only I’d read this then!!).

I was hoping you could clarify your final comments with respect to the time taken to execute the three options. Two of the options I understand:

1. Nested SUMX – It will first look at 1 row in the dates file and iterate over the stores x 500. Repeat 730 times for each date = 500 x 730.

3. SUMMARIZE – It’s just logical, the table is small, the iteration will be tiny.

But… I’m confused on 2. SUMX with Filter. From what I understand, the filter will be executed first and the SUMX second. In this instance

1. Filter is executed, running over 730 lines to validate the filter criteria. Let’s assume this leaves 200 lines that match.

2. SUMX iterator is applied. I thought that this SUMX would be calculated for the 200 lines remaining after the filter.

So I would expect that the number of iterations for SUMX with Filter would be 730 + (200 x 500) rather than 730 + 500 as you mentioned. Any advice you can offer on where my logic has gone wrong would be very much appreciated!

Thanks

Kirsty

This is a complex topic and I am constantly learning and deepening my own understanding. The inefficiency as I understand it is more about the the smaller buckets of execution with SUMX vs the single vertipaq query with SUMMARIZE. While conceptually you can consider iterators like SUMX and FILTER as working row by row, in reality that is not what happens (provided the formula has not been inefficiently written). Generally these iterators will still use vertipaq engine processes to complete the tasks more efficiently than the conceptual “row by row” evaluation suggests. There is an article here (that I haven’t read yet) that may be helpful/insightful. https://www.sqlbi.com/articles/optimizing-nested-iterators-in-dax/