Memory consumption issue while refreshing the data source

1) Check query folding at the step right before Sort/Index

In Power Query, right-click the step → View Native Query.

• If it’s disabled, folding is already broken → sorting/indexing is happening locally.

• Goal: keep folding up to the point where you filter/reduce rows, then do sort/index.

2) Reduce data before sorting/indexing

Apply these as early as possible (while folding still works):

• Filter rows (date range, status, etc.)

• Remove unused columns

• Avoid unnecessary type conversions early

3) If you need stable “row number”, do it at the source (best practice)

If you can change the upstream system:

• Generate row numbers / ordering in the source (SQL/view/service)

• Expose it via OData as a column
  This avoids Power Query doing expensive sorts.