Header promotion in Power BI - Cell-by-Cell Formula Trace

Sample Data

This table shows product names in the first column and their sales numbers in the second column. The first row contains the headers.

Cell	Value
A1	Product
B1	Sales
A2	Apples
B2	100
A3	Bananas
B3	150
A4	Cherries
B4	200

Formula Trace

Table.PromoteHeaders(Source)

Step 1: Source

Step 2: Table.PromoteHeaders(Source)

Cell Reference Map

Product

↓

Apples

↓

Bananas

↓

Cherries

The formula uses the entire table starting at A1:B4. The first row (A1:B1) is promoted to headers.

Result

   Product   Sales
1  Apples    100
2  Bananas   150
3  Cherries  200

After header promotion, the first row becomes column headers. The data rows move up, so 'Apples' is now in row 1 under 'Product'.

Sheet Trace Quiz - 3 Questions

What does the Table.PromoteHeaders function do in this example?

A It deletes the first row.

B It sums the sales numbers.

C It turns the first row into column headers.

D It duplicates the first row.

Key Result

Table.PromoteHeaders shifts the first row to become column headers and moves data rows up.

Practice

1. What does header promotion do in Power BI's Power Query Editor?

easy

A. It removes all empty rows from the data.

B. It turns the first data row into column headers.

C. It filters data based on header names.

D. It merges two tables based on headers.

Solution

1. Step 1: Understand header promotion concept

   Header promotion means using the first row of data as the column headers instead of default generic headers.

2. Step 2: Recognize its use in Power Query

   Power Query's Table.PromoteHeaders function performs this action to make data easier to read and analyze.

3. Final Answer:

   It turns the first data row into column headers. -> Option B

4. Quick Check:

   Header promotion = first row becomes headers [OK]

Hint: Remember: header promotion swaps first row to headers [OK]

Common Mistakes:

• Confusing header promotion with filtering rows
• Thinking it deletes the first row instead of promoting it
• Assuming it merges tables automatically

2. Which of the following is the correct syntax to promote headers in Power Query M language?

easy

A. Table.Promote(SourceHeaders)

B. PromoteHeaders(Table)

C. Source.PromoteHeaders()

D. Table.PromoteHeaders(Source)

Solution

1. Step 1: Recall Power Query function names

   The correct function to promote headers is Table.PromoteHeaders, which takes a table as input.

2. Step 2: Match syntax with options

   Table.PromoteHeaders(Source) uses the correct function and syntax: Table.PromoteHeaders(Source). Other options are invalid or incorrect syntax.

3. Final Answer:

   Table.PromoteHeaders(Source) -> Option D

4. Quick Check:

   Correct function name and syntax = Table.PromoteHeaders(Source) [OK]

Hint: Function starts with Table.PromoteHeaders and takes table input [OK]

Common Mistakes:

• Using incorrect function names like PromoteHeaders alone
• Calling promote headers as a method on source
• Mixing parameter order or names

3. Given this Power Query M code snippet:

let
  Source = Table.FromRows({{"Name", "Age"}, {"Alice", 30}, {"Bob", 25}}),
  Promoted = Table.PromoteHeaders(Source)
in
  Promoted

What will be the column headers of the resulting table?

medium

A. ["Alice", 30]

B. ["Column1", "Column2"]

C. ["Name", "Age"]

D. ["Bob", 25]

Solution

1. Step 1: Analyze the initial table rows

   The first row is {"Name", "Age"}, which looks like header names, followed by data rows.

2. Step 2: Understand effect of Table.PromoteHeaders

   This function uses the first row as column headers, so the columns become "Name" and "Age".

3. Final Answer:

   ["Name", "Age"] -> Option C

4. Quick Check:

   First row becomes headers = ["Name", "Age"] [OK]

Hint: First row values become headers after promotion [OK]

Common Mistakes:

• Thinking default headers remain after promotion
• Confusing data rows as headers
• Assuming column names are generic like Column1

4. You applied Table.PromoteHeaders but got an error saying "Expression.Error: The column 'Name' of the table wasn't found." What is the most likely cause?

medium

A. The first row does not contain valid header names.

B. The data types of columns are incompatible.

C. You used the wrong function name.

D. The table is empty with no rows.

Solution

1. Step 1: Understand error context

   The error "The column 'Name' of the table wasn't found" occurs when code tries to reference [Name] after promotion, but the column doesn't exist.

2. Step 2: Identify promotion effect

   Table.PromoteHeaders sets column names from the first row's values. If 'Name' is missing from the first row, no 'Name' column is created.

3. Final Answer:

   The first row does not contain valid header names. -> Option A

4. Quick Check:

   First row lacks expected header 'Name' [OK]

Hint: Ensure first row contains expected header names like 'Name' [OK]

Common Mistakes:

• Thinking empty table causes this specific column error (promotion fails differently)
• Blaming data types (causes type errors, not missing columns)
• Assuming wrong function (causes syntax error)

5. You imported a CSV file where the first two rows contain metadata, and the third row has actual headers. How do you promote the correct headers in Power Query?

hard

A. Remove the first two rows, then apply Table.PromoteHeaders.

B. Apply Table.PromoteHeaders directly on the original table.

C. Rename columns manually without removing rows.

D. Use Table.Skip to skip the third row, then promote headers.

Solution

1. Step 1: Remove unwanted metadata rows

   The first two rows are metadata, so remove them using Table.Skip(Source, 2) to start from the third row.

2. Step 2: Promote the third row as headers

   After removing the first two rows, apply Table.PromoteHeaders to use the third row as headers.

3. Final Answer:

   Remove the first two rows, then apply Table.PromoteHeaders. -> Option A

4. Quick Check:

   Skip metadata rows before promoting headers [OK]

Hint: Skip metadata rows first, then promote headers [OK]

Common Mistakes:

• Promoting headers without removing metadata rows
• Skipping wrong number of rows
• Renaming columns manually instead of promoting