Forum Discussion
Incorrect Totals
Hi, Thanks for the response.
They are measures, created through other measures in the Projectionfinal table.
- Keegan_Patton3 years agoAdvocate II
I had a similar issue lately, you could try this and see if it works, alot of times a SUMX statement with a nested SUMMARIZE as the table, and calling the measure needed in the 4th argument of SUMMARIZE does the trick, Let me know if that works!
Test =VAR yourmeasure = SUM(your_column)RETURNSUMX(SUMMARIZE('Your Table','Your Table'[Column1],"Calculated",yourmeasure),[Calculated])- Anonymous3 years agoNot applicable
I gave it a try, but ended up with the same data in the table and the same overstated total as before.
I am wondering if I need to address the issue of why there is no total for the Dig Next Week Net at all?
As, it is a part of the Dig Stops calculation. The first three data column's data and totals are correct. The next column's data is correct, but no total. The last column's data is correct, but total is overstated and the same total as the 4th column's.
The date field is from a seperate table, dimdate.
These are the measure, all created in the Projectionfinal table, in case it helps.
- Keegan_Patton3 years agoAdvocate II
I will attempt to replicate those measures in a local dataset I have and see if I can find what the issue is, in the meantime I took a second look at your relationships and realized that you have a bidirectional mant to many between DimDate and UploadAquisitionPlan, is there a specific reason you chose this? That could be causing issues as well.