Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hi guys,
I did a GROUP by transformation for a table in power query, where I had around 4m rows. when loading to Power BI Desktop, I can see in the loading box is evaluating and then loading the 4M rows.
I did this exercise to decrease the loading time, but it doesn't seem it improved (except the size of the dataset has decreased)
Am I doing something wrong, or this is how it supposed to work?
Note: I can do the group by sql statement, but I prefer to have it as a step in power query, in case I wanna go back and check a previous step of the data model, it would be quicker to do in power query than sql
any help would be apprecaited,
Majd
Only in case of Query Folding / Direct Query records are selected at the source database.
Otherwise, all data is imported before any records are selected or grouped in Power Query.
@MarcelBeug thanks for your feedback. It's just the fact that when loarding the model from the query editor to PBI desktop, the data is still loading all row, and once done loading, it will show me just the grouped by/aggregated table.
This has helped by reducing the dataset file size, but loading the data from power query to front end PBI desktop is still the same.
It would be nice and very useful if Group By in Power query can work as the group by statement from the source.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.