Skip to main content
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Frequent Visitor

12-month rolling calculation with another moving date variable (Second Attempt - More Description)

Hi Folks, 

Using September 2021 RS desktop. 


I'm trying to build a measure for 12-month rolling costs, which seemed to work out.


CostR12 = 
Var SelectedMaxDate = MAX ('Claims Costs Transactions'[DatePaidOrAuthorized])
Var MinDate = 
        CALCULATE ( 
            MIN ( 'Date'[Date] ),
            FILTER (
                  ALL ( 'Date' ),
                  DATEADD ( 
                  ) > SelectedMaxDate
      SUM ( 'Claims Costs Transactions'[Amount] ),
      ALL ( 'Date' ),
      'Date'[Date] <= SelectedMaxDate,
      'Date'[Date] >= MinDate






However, I also required the measure to be categorized by another measure which also has a date variable. IF the sum of a field in another table is >=180, the costs should be labeled "Yes". I built a table measure to determine if a 'ReferenceNu' has accumulated enough NbDays by the end of a period. 


Claim Days Paid = 
Var SelectedMaxDateDaysPaid = MAX ('Date'[Date])
        'Days Lost Transactions',
        'Days Lost Transactions'[ReferenceNu],
        "Total Days Paid", SUM('Days Lost Transactions'[NbDays]),
        "180 Day Claim", IF(SUM('Days Lost Transactions'[NbDays])>=180,"Yes","No")
        'Days Lost Transactions',
        'Days Lost Transactions'[DatePaidOrAuthorized] <= SelectedMaxDateDaysPaid
    'Days Lost Transactions',
    'Days Lost Transactions'[PaymentGroupCD] = "COMP"



It isn't working though, and applies the latest result for all periods. For example, for the referencenumber in the image above we should be seeing the result in the table below. As that reference number hasn't acumulated 180 days until Q2 2022.

Year QuarterReferenceNu180 Day Claim
Q4 202120212866No
Q1 202220212866No
Q2 202220212866Yes


Here is my model:




What's the best approach? 

Thanks for taking the time to read through this. 


Super User
Super User


Share the link from where i can download your PBI file and show the expected result very clearly. 

Ashish Mathur

Hi Ashish, 

Here's a link for the .pbix file I'm working with.

Your CostR12 measure can be simplified (even though that may be giving you the correct answer).  Please explain what you want to calculate via that measure.  Then we will go to answering your actual question asked.

Ashish Mathur

Every quarter I need to know see my 12-month rolling costs, which I've done with my COSTR12. 

All of the costs in the 'Claims Costs Transactions' table are associated with claims using the [ClaimantAccountID] or [ReferenceNu] fields, and some of those claims have a sum of [NbDays]>=180  in the 'Days Lost Transactions' table. 

For each of those quarters, I want to be able to visually split the total 12-month rolling cost into cost for 180+ day claims and <180 day claims. The measure needs to sum up the [NbDays] field in the 'Days Paid Transactions' for each [ReferenceNu] IF the [DatePaidorAuthorized] is before the end of the quarter being reported on. So as we move back in time in that line graph, some of those claims have no longer reached that 180 days yet, which in turn moves those costs into the <180 day claim category. 

Frequent Visitor

I referred to "The image above", but it didn't load. Here is the example I'm getting from the current measure.




Helpful resources

Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

July Newsletter

Fabric Community Update - July 2024

Find out what's new and trending in the Fabric Community.