Forum Discussion
numeric slicer for aggregated Y axis
- Anonymous10 months ago
Hi utkarshshastri ,
Thank you for the update.
The “Resources Exceeded” message means Power BI is processing too much data at once, likely because SUMMARIZE with RELATEDTABLE is being used on the large Marketo_Leads and Marketo_Campaign_Activity tables.
To fix this:
Use Power Query’s “Group By” to pre-aggregate data by LEAD_MAIL_DMN_NME and create a summarized table (Lead_Count_Summary_PQ), which helps avoid heavy calculations at runtime.
Alternatively, in DAX, limit summarization to more recent data, for example:
Lead_Count_Summary = VAR RecentLeads = FILTER ( 'Marketo_Leads', 'Marketo_Leads'[MONTH_START] >= DATE(2024,1,1) ) RETURN SUMMARIZE ( RecentLeads, 'Marketo_Leads'[LEAD_MAIL_DMN_NME], "LeadCount", COUNTROWS (RELATEDTABLE('Marketo_Campaign_Activity')) ) If your dataset is currently set to DirectQuery mode, consider changing it to Import mode to help lower the query load.
Let us know if these changes resolve the issue, or if you continue to experience resource limitations. Hope this help you .
Thank you.
Hi utkarshshastri,
Thank you for sharing the relationship details — that helps a lot.
Based on your model (Marketo_Campaign_Activity → Marketo_Leads via LEAD_ID ↔ SRC_LEAD_IDN`), you can try creating a summarized table instead of using a measure. This approach improves performance and enables a numeric “Between” slicer directly.
Lead_Count_Summary =
SUMMARIZE (
'Marketo_Leads',
'Marketo_Leads'[LEAD_MAIL_DMN_NME],
"LeadCount", COUNTROWS (RELATEDTABLE('Marketo_Campaign_Activity'))
)
Once after creating please do the following :
- Add LeadCount from this table into a slicer and set it to Between.
- Connect the slicer to your main visual using LEAD_MAIL_DMN_NME or the appropriate account field.
- This method filters pre-aggregated data, so it should be much faster than parameter-based filtering.
Please note, since screenshots don’t include the data rows or DAX error details, we can’t fully reproduce the issue on our side, but the logic above aligns with your model structure.
If you still face an issue, kindly share the exact error message or a few sample rows to help validate further.
Thank you.
its showing query has exceeded
- Anonymous10 months agoNot applicable
Hi utkarshshastri ,
Thank you for the update.
The “Resources Exceeded” message means Power BI is processing too much data at once, likely because SUMMARIZE with RELATEDTABLE is being used on the large Marketo_Leads and Marketo_Campaign_Activity tables.
To fix this:
Use Power Query’s “Group By” to pre-aggregate data by LEAD_MAIL_DMN_NME and create a summarized table (Lead_Count_Summary_PQ), which helps avoid heavy calculations at runtime.
Alternatively, in DAX, limit summarization to more recent data, for example:
Lead_Count_Summary = VAR RecentLeads = FILTER ( 'Marketo_Leads', 'Marketo_Leads'[MONTH_START] >= DATE(2024,1,1) ) RETURN SUMMARIZE ( RecentLeads, 'Marketo_Leads'[LEAD_MAIL_DMN_NME], "LeadCount", COUNTROWS (RELATEDTABLE('Marketo_Campaign_Activity')) ) If your dataset is currently set to DirectQuery mode, consider changing it to Import mode to help lower the query load.
Let us know if these changes resolve the issue, or if you continue to experience resource limitations. Hope this help you .
Thank you.
- Anonymous10 months agoNot applicable
Hi utkarshshastri ,
We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.Thank you.