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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
Anonymous
Not applicable

TOTALYTD Fails to return a running total.

I've reviewed similar posts but I can't seem to find a solution to my specific problem with TOTALYTD not producing a running total. I have a simple fact table and date dimension (calendar table) joined with a one-to-many relationship. When I use the this forumla:

YTDRevenue = TOTALYTD(SUM(FactGeneralLedger[Revenue]), DimDate[Date])

 

I recieve this line chart using the DimDate[Date] column as the axis 

 



The formula is only reporting the sum of revenue by each month, not a running total as desired. I suspect the join but I can get the correct totals in SQL just fine. The tables are joined on a column called [DateKey] and then linked in the model. I then filter all items off DimDate[Date] which is a full DateTime stamp.

relationship

What do I need to change to achieve and actual running total?

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Thanks for the reply Greg. I was pretty stubborn since what I'm trying to achieve (use my existing date table in the data warehouse) was very simple I figured there had to be a way. After a ton of heartache of formulas all not adding up I finally found the issue. I had to manually mark my Date Dimension table as a date table. Evidently PowerBI trys to guess these tables but since I used a Integer as my primary key, 20190212 for example, it could not parse it and I have to manually set it up as shown below:

https://docs.microsoft.com/en-us/power-bi/desktop-date-tables

 

If I run into issue in the future I"ll take a look at your formulas.

 

 

 

 

View solution in original post

2 REPLIES 2
Greg_Deckler
Community Champion
Community Champion

See if my Time Intelligence the Hard Way provides a different way of accomplishing what you are going for.

https://community.powerbi.com/t5/Quick-Measures-Gallery/Time-Intelligence-quot-The-Hard-Way-quot-TIT...



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...
Anonymous
Not applicable

Thanks for the reply Greg. I was pretty stubborn since what I'm trying to achieve (use my existing date table in the data warehouse) was very simple I figured there had to be a way. After a ton of heartache of formulas all not adding up I finally found the issue. I had to manually mark my Date Dimension table as a date table. Evidently PowerBI trys to guess these tables but since I used a Integer as my primary key, 20190212 for example, it could not parse it and I have to manually set it up as shown below:

https://docs.microsoft.com/en-us/power-bi/desktop-date-tables

 

If I run into issue in the future I"ll take a look at your formulas.

 

 

 

 

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors