Running total chart

The numbers seem to be off slightly with this.

 CALCULATE(SUM(Query20[NET_CONTRIBUTIONS]),FILTER(ALL(Query20[DATE]),Query20[DATE] <=MAX(Query20[DATE])))

OscJara as I pointed out earlier, the examples given here use a separate date table. tmullady's last formula was incorrect because it is referring to dates in the same table, not using a relationship to a dedicated date table as the examples showed. You're doing the same thing.

In your formula, this argument:

MAX(TResponses[Date of Activity - Valida])

...returns the maximum date of activity in the current filtering context, not the maximum date overall. Maybe it would help to see how the two formulas translate to plain English.

Code:

ACC AVGPoints = CALCULATE(
	SUM(TResponses[AVG Points]),
	FILTER(
		ALL(TResponses[Date of Activity - Valida]),
		TResponses[Date of Activity - Valida] <= MAX(TResponses[Date of Activity - Valida])
	),
	VALUES(TResponses[AVG Points])


Translation:

ACC AVGPoints = give me the sum of TResponses[AVG Points] for all rows that match...
...the set of all rows in the entire Date of Activity - Valida column...
...where the Date of Activity - Valida is less than or equal to the latest Date of Actvity - Valida
 in the current filter context...
...VALUES(TResponses[AVG Points]) just returns a column of all unique rows from that column
 and I don't think it really accomplishes anything here because those values are already called
 by the SUM at the beginning. 

I believe the problem is that because the filter context is coming from the OrderWeek column on the same table, you're implicitly passing another filter statement to that formula that essentially says, "Also filter TResponses to only the rows matching the current OrderWeek context on this chart" which effectively nullifies the ALL part of your formula.

Read the cumulative total article linked above and look at how it's done there. The example works if you do it the way the example demonstrates.