Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowTry your skills in the Power BI Dataviz World Championship! Round one ends June 26. Join now
Hi @Anonymous
User-defined aggregations in Power BI serve the primary purpose of improving query performance, especially when working with large DirectQuery semantic models.
They achieve this by caching data at an aggregated level in memory, allowing Power BI to retrieve summarized data from the cache rather than executing potentially slow queries against the underlying data source for every visual interaction.
It is oftenly used with dual storage mode, if you are using a large model, you can create an aggregation table for your import dataset and use a direct query to get the details of the last transactions
Radcad wrote some usefuls articles about this topic:
Let me know if you need more help to understand this concept
Hi @Anonymous
User-defined aggregations in Power BI serve the primary purpose of improving query performance, especially when working with large DirectQuery semantic models.
They achieve this by caching data at an aggregated level in memory, allowing Power BI to retrieve summarized data from the cache rather than executing potentially slow queries against the underlying data source for every visual interaction.
It is oftenly used with dual storage mode, if you are using a large model, you can create an aggregation table for your import dataset and use a direct query to get the details of the last transactions
Radcad wrote some usefuls articles about this topic:
Let me know if you need more help to understand this concept
| User | Count |
|---|---|
| 22 | |
| 20 | |
| 19 | |
| 19 | |
| 11 |
| User | Count |
|---|---|
| 63 | |
| 53 | |
| 46 | |
| 44 | |
| 31 |