Why Query folding in Power Query in Power BI? - Purpose & Use Cases

The Big Idea

What if your slow data reports could run lightning fast with just a simple trick?

The Scenario

Imagine you have a huge table with thousands of rows in your database. You want to filter and sort this data before loading it into Power BI. Doing this manually means downloading all the data first, then filtering and sorting it inside Power BI.

The Problem

This manual way is slow because you move all data over the network, even the parts you don't need. It wastes time and computer power. Also, if the data changes, you have to repeat the whole slow process again.

The Solution

Query folding lets Power Query send your filter and sort steps back to the database. The database does the heavy work and sends only the needed data. This makes your reports faster and uses less computer power.

Before vs After

✗ Before

Load full table
Filter rows in Power Query
Sort rows in Power Query

✓ After

Write filter and sort steps
Power Query sends these to database
Database returns only filtered, sorted data

What It Enables

It enables fast, efficient data loading by pushing transformations to the data source automatically.

Real Life Example

A sales manager wants to see only last month's sales from a huge database. With query folding, only last month's data is fetched, making the report load quickly.

Key Takeaways

Manual data filtering after loading is slow and inefficient.

Query folding pushes filters and sorts to the database.

This speeds up data refresh and reduces resource use.

Practice

1. What is query folding in Power Query?

easy

A. It pushes data transformations back to the data source for faster processing.

B. It copies all data locally before applying transformations.

C. It disables all data refresh options.

D. It automatically creates charts from data.

Solution

1. Step 1: Understand the concept of query folding

   Query folding means Power Query sends transformation steps back to the data source to run there.

2. Step 2: Compare options with this definition

   Only It pushes data transformations back to the data source for faster processing. describes pushing transformations to the source for speed.

3. Final Answer:

   It pushes data transformations back to the data source for faster processing. -> Option A

4. Quick Check:

   Query folding = pushing steps to source [OK]

Hint: Query folding means running steps at the source, not locally [OK]

Common Mistakes:

• Thinking query folding copies data locally first
• Confusing query folding with data visualization
• Believing query folding disables refresh

2. Which of the following Power Query steps supports query folding?

easy

A. Adding a custom column with complex M code referencing external files

B. Creating a manual index column

C. Merging queries with a local Excel table

D. Filtering rows based on a column value

Solution

1. Step 1: Identify steps that can be folded

   Simple filters on source columns usually fold back to the database.

2. Step 2: Analyze other options

   Custom columns with external references, merges with local tables, and manual indexes break folding.

3. Final Answer:

   Filtering rows based on a column value -> Option D

4. Quick Check:

   Filters fold, complex custom steps don't [OK]

Hint: Simple filters fold; complex or local steps usually don't [OK]

Common Mistakes:

• Assuming all steps fold automatically
• Thinking merges with local tables fold
• Believing manual indexes fold

3. Given this Power Query M code, which step breaks query folding?

let
  Source = Sql.Database("Server", "DB"),
  FilteredRows = Table.SelectRows(Source, each [Status] = "Active"),
  AddedCustom = Table.AddColumn(FilteredRows, "Custom", each Text.Length([Name]))
in
  AddedCustom

medium

A. Source step

B. FilteredRows step

C. AddedCustom step

D. None, all steps fold

Solution

1. Step 1: Check each step for folding support

   Source connects to SQL, supports folding. Filtering rows on a column also folds.

2. Step 2: Analyze the AddedCustom step

   Adding a custom column with a function like Text.Length is done locally and breaks folding.

3. Final Answer:

   AddedCustom step -> Option C

4. Quick Check:

   Custom columns break folding [OK]

Hint: Custom columns usually break folding; filters don't [OK]

Common Mistakes:

• Thinking all steps fold if source is SQL
• Assuming filters break folding
• Ignoring custom column impact

4. You notice your Power Query refresh is slow. Which fix helps restore query folding?

medium

A. Replace a custom column step with a simple filter step

B. Add a manual index column before filtering

C. Merge with a local Excel table before filtering

D. Disable the data source privacy settings

Solution

1. Step 1: Identify what breaks folding

   Custom columns and merges with local tables break folding and slow refresh.

2. Step 2: Choose a fix that restores folding

   Replacing custom columns with simple filters allows folding to resume.

3. Final Answer:

   Replace a custom column step with a simple filter step -> Option A

4. Quick Check:

   Simple filters restore folding, custom steps break it [OK]

Hint: Use filters instead of custom columns to keep folding [OK]

Common Mistakes:

• Adding manual indexes early breaks folding
• Merging with local tables breaks folding
• Thinking privacy settings affect folding

5. You want to optimize a Power Query that merges a SQL table with a large local Excel table. How can you maximize query folding?

hard

A. Load the local Excel table to SQL before merging

B. Filter the SQL table first, then merge with the local Excel table

C. Merge first, then filter the combined table

D. Disable query folding to avoid errors

Solution

1. Step 1: Understand folding with merges

   Merging with local tables breaks folding, but filtering source first keeps folding for that part.

2. Step 2: Choose the best approach

   Filtering SQL table before merging reduces data and preserves folding on the source side.

3. Final Answer:

   Filter the SQL table first, then merge with the local Excel table -> Option B

4. Quick Check:

   Filter source before merge to keep folding [OK]

Hint: Filter source data before merging with local tables [OK]

Common Mistakes:

• Merging before filtering breaks folding early
• Assuming disabling folding helps performance
• Not considering loading local data to SQL