Query folding in Power Query in Power BI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a query that folds by referencing the source table.

Power BI

let Source = Sql.Database("ServerName", [1]) in Source

Drag options to blanks, or click blank then click option'

A"DatabaseName"

B"TableName"

C"QueryName"

D"ServerName"

Attempts:

3 left

💡 Hint

Common Mistakes

Using the server name twice instead of the database name.

Using the table name instead of the database name.

The Sql.Database function requires the database name as the second argument to connect and enable query folding.

2fill in blank

medium

Complete the code to filter rows where the column "Status" equals "Active" and keep query folding.

Power BI

let FilteredRows = Table.SelectRows(Source, each [Status] [1] "Active") in FilteredRows

Drag options to blanks, or click blank then click option'

A!=

B=

C<>

D>

Attempts:

3 left

💡 Hint

Common Mistakes

Using inequality operators which filter out the desired rows.

Using comparison operators like < or > which do not apply to text.

The = operator filters rows where the "Status" column exactly matches "Active".

3fill in blank

hard

Fix the error in the code to keep query folding when adding a calculated column doubling the "Sales" value.

Power BI

let AddedColumn = Table.AddColumn(Source, "DoubleSales", each [Sales] [1] 2) in AddedColumn

Drag options to blanks, or click blank then click option'

A-

B+

C*

D/

Attempts:

3 left

💡 Hint

Common Mistakes

Using addition instead of multiplication.

Using division or subtraction which do not double the value.

To double the sales value, multiply the "Sales" column by 2 using the * operator.

4fill in blank

hard

Fill both blanks to create a query folding step that groups rows by "Category" and sums "Amount".

Power BI

let GroupedRows = Table.Group(Source, [1], {{"TotalAmount", [2], "Amount"}}) in GroupedRows

Drag options to blanks, or click blank then click option'

A{"Category"}

BList.Sum

CTable.Sum

DSum

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a list for grouping columns.

Using a non-existent function like Table.Sum.

Grouping requires a list of columns, so use {"Category"}. To sum values, use the function List.Sum.

5fill in blank

hard

Fill the blanks to create a query folding step that filters rows where "Date" is after 2023-01-01 and selects only "ID" and "Date" columns.

Power BI

let Filtered = Table.SelectRows(Source, each [Date] [1] #date(2023, 1, 1)), Selected = Table.SelectColumns(Filtered, [2]), Result = Selected in Result

Drag options to blanks, or click blank then click option'

A>

B{"ID", "Date"}

C{"Date", "ID"}

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using < which filters dates before 2023-01-01.

Using a string instead of a list for columns.

Use > to filter dates after 2023-01-01. The columns to select must be a list, so {"ID", "Date"} is correct.

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