ExamplesFor You
Home / Power Query / List.Sum

🔄 Power Query example

List.Sum examples in Power Query

Learn practical Power Query List.Sum examples with M code, UI steps, common mistakes, FAQs and copy-ready transformation patterns.

Updated 2026-06-125 practical examplesCopy-ready M code

💡 Ideas for You

Learning resources for Power Query, data cleaning and repeatable reporting.

4 useful links

Some links in this section may be affiliate links. Choose only what is useful for your own work.

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

List.Sum([Sales])

Typical UI steps

  1. Open Power Query Editor.
  2. Select the relevant column or query.
  3. Apply the transformation from the ribbon or formula bar.
  4. Review the generated step.
  5. Check data types and row counts before loading.
✍️

5 practical examples

1

Use List.Sum in a sales report

This example shows how to use List.Sum when preparing a sales report.

List.Sum([Sales])

Use this pattern when the sales report needs a repeatable transformation instead of manual cleanup.

2

Use List.Sum in a customer list

This example shows how to use List.Sum when preparing a customer list.

List.Sum([Amount])

Use this pattern when the customer list needs a repeatable transformation instead of manual cleanup.

3

Use List.Sum in a inventory export

This example shows how to use List.Sum when preparing a inventory export.

List.Sum([Units])

Use this pattern when the inventory export needs a repeatable transformation instead of manual cleanup.

4

Use List.Sum in a monthly dashboard

This example shows how to use List.Sum when preparing a monthly dashboard.

List.Sum([Revenue])

Use this pattern when the monthly dashboard needs a repeatable transformation instead of manual cleanup.

5

Use List.Sum in a operations tracker

This example shows how to use List.Sum when preparing a operations tracker.

List.Sum([Hours])

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.

Related Power Query examples

🔄 Table.SelectRows🔄 Table.AddColumn🔄 Table.TransformColumnTypes🔄 Table.RenameColumns🔄 All Power Query examples

FAQ

When should I use List.Sum in Power Query?

Use List.Sum when the transformation should be repeatable every time the data refreshes.

Can I do List.Sum 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.