When to use this Power Query pattern
Use this pattern when the same data preparation step needs to happen every time a file, table or report refreshes.
Syntax or pattern
Table.Group(Source, {"Region"}, {{"Total Sales", each List.Sum([Sales]), type number}})Typical UI steps
- Select the grouping column.
- Choose Group By.
- Add aggregations such as Count Rows or Sum.
- Rename summary columns.
- Check totals before loading.
5 practical examples
Use Table.Group in a sales report
This example shows how to use Table.Group when preparing a sales report.
Table.Group(Source, {"Region"}, {{"Total Sales", each List.Sum([Sales]), type number}})Use this pattern when the sales report needs a repeatable transformation instead of manual cleanup.
Use Table.Group in a customer list
This example shows how to use Table.Group when preparing a customer list.
Table.Group(CleanSource, {"Department"}, {{"Total Amount", each List.Sum([Amount]), type number}})Use this pattern when the customer list needs a repeatable transformation instead of manual cleanup.
Use Table.Group in a inventory export
This example shows how to use Table.Group when preparing a inventory export.
Table.Group(Inventory, {"Region"}, {{"Total Units", each List.Sum([Units]), type number}})Use this pattern when the inventory export needs a repeatable transformation instead of manual cleanup.
Use Table.Group in a monthly dashboard
This example shows how to use Table.Group when preparing a monthly dashboard.
Table.Group(ReportData, {"Region"}, {{"Total Revenue", each List.Sum([Revenue]), type number}})Use this pattern when the monthly dashboard needs a repeatable transformation instead of manual cleanup.
Use Table.Group in a operations tracker
This example shows how to use Table.Group when preparing a operations tracker.
Table.Group(Tracker, {"Region"}, {{"Total Hours", each List.Sum([Hours]), type number}})Use this pattern when the operations tracker needs a repeatable transformation instead of manual cleanup.
Common mistakes to avoid
- Applying steps in an order that makes later cleaning harder.
- Forgetting that step names are referenced by later M code.
- Not checking row counts before and after transformations.
FAQ
When should I use Table.Group in Power Query?
Use Table.Group when the transformation should be repeatable every time the data refreshes.
Can I do Table.Group from the Power Query interface?
Usually yes. The interface creates the M code for many common transformations, and you can adjust it in the formula bar or Advanced Editor.
Should I edit the M code manually?
Edit M manually when the interface cannot express the pattern clearly, or when you need reusable logic, parameters or cleaner step names.