Rolling 12 Months in Power Query

Last week, in a blog comment, a reader asked how to filter their data to only show the most recent rolling 12 month period.  This post looks at how I made that work in Power Query.


Assume we have a table set up as follows:

As you can see, we have sales categories down the left, months across the top, and values in the middle.  A classic setup when users are tracking information.  And now we need to pull the most recent 12 months only from that table.

You can download the completed sample file if you’d like to follow this along as well.

Filter the most recent rolling 12 months from a table in Power Query

Step 1: Grab the data

First thing we need to do is grab the data. To do this, I clicked in the table and:

  • Power Query –> From Table –> Confirm the range (if required)
  • Changed the query name to Rolling12

Helpfully, Power Query identified the data types in all the columns for me, so I’m pretty much ready to go.

Step 2: Show the most recent record first

To do this, we really need to get the data into an unpivoted list.  Easy enough to do:

  • Select the “Sales” column
  • Right click –> UnPivot Other Columns

Note: The “unpivot other columns” command was added to the right click menu in version 2.24.  While you can most likely still access this command, you are definitely running an older version, and for a multitude of important reasons, you should really update to the latest version of Power Query.

If you don’t want to (or can’t) do this for some reason, then go to Transform –> Unpivot –> Unpivot Other columns to accomplish the same thing.

We now get a nice unpivoted list:


Next I cleaned up that Attribute column:

  • Right click the Attribute column –> Rename –> Date
  • Right click the Date column –> Changed Type –> Date

And finally I sorted the records to show the most recent ones at the top:

  • Click the Filter icon on the Date column –> Sort Descending

Leaving us with this:


Step 3: Create variables to hold the required data range

Next we need to work out the dates that we want to use for the top and bottom range of dates in the query.  This is a bit tricky, but uber powerful once you realize you can do it.

To start, click the fx icon in the formula bar:


NOTE: If you don’t see the formula bar, go to the View tab, and check the box next to Formula Bar

What this does is add a new step in the formula bar called “Custom1”.  And if you check the formula bar you’ll see that it just refers to the previous step:


The cool thing here is that we can modify this.  Why don’t we add some data to the end of that statement to pull the first value from the Date column of that table?  To do that, change the text in the formula bar to read as follows:

=#”Sorted Rows”[Date]{0}

Recognize here that:

  • #”Sorted Rows” refers to the table in the previous step
  • [Date] tells Power Query that you only want the Date column
  • {0} tell Power Query that you want the first value from that column (remember that Power Query starts counting from 0)

The result is a single cell with the most recent date:


Let’s keep things clean in our Steps window… right click the Custom1 step and rename it to “MaxDate”.


What’s cool here is that we’ve essentially created a variable to work out and hold the most recent date.

So now that we have the top of the range, why don’t we create another step to modify it to the date for the lower end of the range?

  • Click the fx step in the formula bar
  • Modify the formula to read as follows


And the result is a new Custom1 step that shows in the formula bar as follows:


Note:  The formulas you can use are documented at Microsoft’s site here:

Pretty cool, don’t you think?  We’ve now got a step that holds the lower end of the results too.  Let’s do our cleanup again.

Right click the Custom1 step and rename it to “AfterDate”

Step 4: Implement the variables into a filter

Our last step is to implement the variables into the filter, cutting the data down to the most recent rolling 12 months of data.  Before we can do that, however, we really need to get back to the table we had in the “Sorted Rows” step.

The challenge is that we can’t select and work from that step, as it’s earlier in the process than the creation of our variables.  So how do we get back to that step AFTER we’ve created our variables?

  • Click the fx button in the formula bar

Once again, we get a new step in the formula bar:


The problem is that it’s referring to the previous step.  So what if we changed it to point to the #”Sorted Rows” step?


Now how cool is that?  Not only can we refer to the previous step of our query, we can change that to point to ANY previous step, or type in our own formulas against any previous step!

NOTE:  If your steps have spaces in the, don’t forget to wrap the step name in quotes and then preface it with the # symbol.  If your steps don’t have spaces, then you don’t need to do this.

Okay, so now let’s filter our data.  We’ll start by doing it manually:

  • Click the filter icon on the Date column
  • Select Date Filters –> Custom Filter
  • Set up your filter as follows:


Notice that we have to pick the values from the list here.  (Wouldn’t it be cool if we could type in our variable names here?  That would be awesome!)  Regardless, we can set up the filter as we’d expect to use it.  This will filter our list, and leave us with the following formula in the formula bar:


NOTE:  You can expand the formula bar to show as I have by clicking the little down arrow icon.

Good stuff… now we need to do a little surgery.  Let’s replace the manual dates with our variables:

= Table.SelectRows(Custom1, each [Date] <= MaxDate and [Date] > AfterDate)

If you check the table now, you’ll see that it is filtered down to only contain records between Mar 1, 2014 and Feb 28, 2015.  And better yet, because the variables are created dynamically when the query is run, it will ALWAYS return the most recent rolling 12 months!

Step 5: Pivoting the data back into the original format.

Now we need to put the data back into the format the user wanted.  To do this, we need to pivot it back.

The trick to pivoting in Power Query is to select the column you want to use as the new column headers.  This time it is the Date column.  So…

  • Select the Date column –> Transform –> Pivot Column
  • Change the “Values” column to the one that holds your values (in this case it’s actually called Value)


And the result:


Bingo!  The most recent rolling 12 months of data from our table.

At the point you can click File –> Close & Load, and load it to a table.

Proof Positive

Go and add a new column of data.  You can insert it into the existing table, put it on the end, it really doesn’t matter since Power Query will sort it anyway.  Once you’re done, right click the new table and refresh it, and you’ll find it works nicely.

One minor point of note… in the version I did we’ve actually reversed the column order (the most recent date has moved to the left from the right.)  If we wanted to change that it’s fairly easy too.  Just before we pivot the data back into the pivoted form, just sort it in descending order.



22 thoughts on “Rolling 12 Months in Power Query

  1. =#”Sorted Rows”[Date]{0} is brilliant. I can cut a couple of steps out of my other queries that remove all other columns and keeps only the top row. Thanks!

  2. Excellent post Ken. I knew you could refer to previous lines in the process flow, and also that you could rename the steps, but you have explained it really well. I will definitely be using these steps moving forward.

  3. Awesome post Ken. One of your best!!!!!

    You document these posts so well, making steps easy to follow and adding screenshots to confirm the results. You have confirmed a lot of cool processes in this post; jumping to previous steps (so cool and useful!!), customizing the formulas in the formula bar (noting that one does not have to go back to the Adv. Editor every time if it's just single line edits) and creating and using variables. Brilliant.

    This post is being saved for definite future referencing!!
    Please keep up the great work and amazing posts in your blog. Its such a great resource. Your time and effort is definitely appreciated on this side of the world! Cheers!!

  4. Thanks Ken 🙂
    And here is another "easy to follow" way.. ;-). M is fantastic !! Only two steps
    Source = Excel.CurrentWorkbook(){[Name="Table1"]}[Content],
    Rolling12 = Table.SelectColumns(Source, List.Combine({{"Sales"}, List.FirstN( List.Reverse(Table.ColumnNames(Source)),12)}) )


  5. hehe.. 🙂
    Ken, I just wanted to show that it is worth to learn the M code 🙂

  6. Thanks so much for this tutorial.. its great to see what PowerQuery can do if you get to know how the M-formulas work.

  7. Great post !

    Is it possible to get the last date and use it as Parameter for another table?

  8. Hi MP,

    I'm sure you could, but I'd suggest that you call that value from the other table using something like this (untested):
    LastDate = List.Last(QueryName[ColumnName])

  9. Thank you for the post! It was a big help. Curious if you could add a condition to the AfterDate. I've tried a couple variations of this, but no joy yet.

    = if [Sales] = "Spade" then Date.AddMonths(MaxDate, -6) else Date.AddYears(MaxDate, -1)

  10. Hi Ken, This is fantastic and so easy to follow. I modified it slightly to do a rolling 13 months using = Date.AddMonths(MaxDate,-13) and it works perfectly. Now it is all set up this saves me so much time. Thank you

  11. Thank you so much for this, Ken. I've been manually updating in Power Query and I knew there must be a method for a dynamic rolling 28 days. I'm going to repeat this method in a second report which uses epoch dates.

    Glad you had this article as I left your book at home!

  12. Ken, thank you for this excellent article. Additionally, I appreciated Bill Szysz's concise solution, which can be further shortened as follows:
    Source = Excel.CurrentWorkbook(){[Name="Table1"]}[Content],
    Rolling12 = Table.SelectColumns(Source, {"Sales"}&List.FirstN( List.Reverse(Table.ColumnNames(Source)),12))

  13. However, since you consistently prioritize the UI, I'd like to propose a UI solution that eliminates the need for any manual M code, as outlined below.

    Source = Excel.CurrentWorkbook(){[Name="Table1"]}[Content],
    #"Demoted Headers" = Table.DemoteHeaders(Source),
    #"Duplicated Column" = Table.DuplicateColumn(#"Demoted Headers", "Column1", "Column1 - Copy"),
    #"Transposed Table" = Table.Transpose(#"Duplicated Column"),
    #"Reversed Rows" = Table.ReverseRows(#"Transposed Table"),
    #"Kept First Rows" = Table.FirstN(#"Reversed Rows",13),
    #"Transposed Table1" = Table.Transpose(#"Kept First Rows"),
    #"Promoted Headers" = Table.PromoteHeaders(#"Transposed Table1", [PromoteAllScalars=true])
    #"Promoted Headers"

  14. Clever Mahmoud! Interestingly, in testing this with 500 rows, the perf difference between your (UI version) and Bill's (M version) solutions are very close (less than 1 sec), where my original is much higher (avg 3.7, median 2, range 1.5-6.9 sec).

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Latest Posts