DAX Query help

krish42 

Result AmountMST = 
SUMX(
FILTER(CustTrans, CustTrans[TANSDATE] <= MAX('Calendar'[Date])),
VAR SettleAdj = RELATED(CustSettlements[EXCHADJUSTMENT])
RETURN
SWITCH(TRUE(),
CustTrans[TRANSTYPE] = 9, CustTrans[AMOUNTMST],
CustTrans[EXCHADJUSTMENT] = 0 && SettleAdj <> 0, CustTrans[AMOUNTMST] - SettleAdj,
CustTrans[AMOUNTMST] + CustTrans[EXCHADJUSTMENT]
)
)

If this answer helped, please click 👍 or Accept as Solution.
-Kedar
LinkedIn: https://www.linkedin.com/in/kedar-pande

Hi krish42,

Please include, in a usable format, not an image, a small set of rows for each of the tables involved in your request and show the data model in a picture, so that we can import the tables in Power BI and reproduce the data model. The subset of rows you provide, even is just a subset of the original tables, must cover your issue or question completely. Alternatively, you can share your .pbix via some cloud service and paste the link here. Do not include sensitive information and do not include anything that is unrelated to the issue or question. Please show the expected outcome based on the sample data you provided and make sure, in case you show a Power BI visual, to clarify the columns used in the grouping sections of the visual.

Need help uploading data? click here

Want faster answers? click here

If this helped, please consider giving kudos and mark as a solution

@me in replies or I'll lose your thread

Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page

Consider voting this Power BI idea

Francesco Bergamaschi

MBA, M.Eng, M.Econ, Professor of BI

Hi krish42  ,
Thanks for reaching out to the Microsoft Fabric Community forum.

The error is occurring because the DAX measure is forcing the engine to generate and process a very large intermediate result set during query execution, which exceeds the 15MB per-query data limit enforced by the Tabular engine.

As an immediate workaround, you can try reducing the dataset being evaluated before running the measure. For example:

• Apply a date filter (e.g., specific month or year) in the report using slicers.
• Filter by a specific AccountNum or a smaller customer subset.
• Use report-level or page-level filters to limit the number of transactions loaded into the visual.
• Temporarily test the measure on a smaller date range to confirm it works correctly.

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

Hello krish42, 

The resource issue is caused by using [Settlement Exch Adj] inside SUMX over CustTrans.

When a measure is evaluated inside an iterator, DAX performs a context transition and may repeatedly scan the related table for every row. With large tables this can exhaust resources.

Microsoft documentation:

Row context and filter context in DAX
https://learn.microsoft.com/dax/row-context-and-filter-context-in-dax

CALCULATE function (context transition)
https://learn.microsoft.com/dax/calculate-function-dax

SUMX function
https://learn.microsoft.com/dax/sumx-function-dax

To resolve this, avoid calling settlement measures inside SUMX.
Instead, calculate the exchange adjustment per transaction using the relationship.

Result Amount

Result Amount :=
VAR AgedDebtDate = MAX ( 'Calendar'[Date] )
RETURN
CALCULATE (
    SUMX (
        CustTrans,
        VAR BaseAmount = CustTrans[AMOUNTMST]
        VAR TransExch = CustTrans[EXCHADJUSTMENT]
        VAR SettlementExch =
            CALCULATE (
                SUM ( CustSettlements[EXCHADJUSTMENT] ),
                CustSettlements[TRANSDATE] <= AgedDebtDate
            )
        VAR FinalExch =
            IF (
                TransExch = 0 && SettlementExch <> 0,
                SettlementExch,
                TransExch
            )
        RETURN
            BaseAmount + FinalExch
    ),
    CustTrans[TRANSDATE] <= AgedDebtDate
)

Settlement Amount

Settlement Amount :=
VAR AgedDebtDate = MAX ( 'Calendar'[Date] )
RETURN
CALCULATE (
    SUM ( CustSettlements[SETTLEAMOUNTMST] ),
    CustSettlements[TRANSDATE] <= AgedDebtDate
)

Final Balance

Balance GBP :=
ROUND (
    [Result Amount] - [Settlement Amount],
    2
)

Why this works:

• The settlement exchange adjustment is evaluated within the transaction row context via the relationship
• No external measure is called inside the iterator
• Date filtering is applied correctly
• Eliminates repeated scans of CustSettlements

This follows Microsoft guidance on context transition and iterator performance and should resolve the resource error.

Hi krish42 

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.

Hi krish42 

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