Data is skipped in Sum Totals

[tracyb]

I have a report that has data for multiple years.  For some reason all the previous years data for the month of December is not calculated and that column has the totals for Jan-Nov, then the Total Column is $0.  If I am in the current year, I can get the correct total.  For example, in this report this past December, it was showing the correct December totals, but once the new year switched over I get this.  This report has been in existence for a number of years, and I have recently taken over responsibility for it.  I do not know if this was always the problem.  I really don't know where to start.

[GilbertQ · Accepted solution]

Hi @tracyb 

What I would recommend doing is looking through the data and potentially there is either no numbers for December or if you are using a date table with a relationship have a look to make sure that you have dates for the December. you are looking at. Otherwise, you could use Performance Analyzer in Power BI Desktop to get the DAX query and then run it in the query view to see what the DAX is actually doing and potentially investigate it that way.

[v-nmadadi-msft]

Hi @tracyb 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-nmadadi-msft]

Hi @tracyb 
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-nmadadi-msft · Accepted solution]

Hi @tracyb ,

What’s most likely happening with the total here is that the measure behind this report is written in a way that depends on the current year or a specific month filter being present. When Power BI calculates the Total column, it doesn’t just add up what you see in the rows it re-evaluates the measure in a broader filter context. If the DAX logic expects something like the “current year” (for example, using YEAR(TODAY())) or relies on a month being selected, that logic can fail when the year rolls over or when the total is calculated without a specific month filter. When that condition fails, the measure often returns a blank value, which shows up as $0 in the visual. That would explain why December worked fine during the year itself but looks incorrect once the new year begins.

To resolve this, I would recommend reviewing the DAX measure used in the visual and removing any logic that depends on the previous calendar year. Instead, ensure the calculation relies purely on the filter context coming from the Date table (for example, using standard time-intelligence functions like TOTALYTD or DATESYTD without tying them to the current year). This will allow prior years to calculate correctly regardless of when the report is viewed.

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[GilbertQ · Accepted solution]

Hi @tracyb 

What I would recommend doing is looking through the data and potentially there is either no numbers for December or if you are using a date table with a relationship have a look to make sure that you have dates for the December. you are looking at. Otherwise, you could use Performance Analyzer in Power BI Desktop to get the DAX query and then run it in the query view to see what the DAX is actually doing and potentially investigate it that way.