Forum Discussion
More efficient running total column in Power Query?
Hi, RMDNA
I think you may misunderstood what I meant.This is not a problem that can be solved by optimization.
You can refer to this wonderful blog:
comparing-dax-calculated-columns-with-power-query-computed-columns
The Power Query computed columns are not suitable for executing the aggregation on the data source, you should consider a DAX calculated column to avoid a long processing times.
Best Regards,
Community Support Team _ Eason
Hi, RMDNA
I think you may misunderstood what I meant.This is not a problem that can be solved by optimization.
You can refer to this wonderful blog:
comparing-dax-calculated-columns-with-power-query-computed-columns
The Power Query computed columns are not suitable for executing the aggregation on the data source, you should consider a DAX calculated column to avoid a long processing times.
Best Regards,
Community Support Team _ Eason
So you're saying is best to use the DAX calculated column, but I do run into an issue doing so. My problem is that I'm using a high amount of rows (~100,000) that I need to perform a running total and I refresh the report I get a memory error, "There's not enough memory to complete this operation. Please try again later when there may be more memory available."
The PBI file size is 17MB and I know that is not the problem, what the problem is I know for sure in the running total calculation because when I take those out, the report refreshes with no problem.
Do you have a suggestion to have running totals with no problem despite the amount of the data?
Your help is much appreciated.