Query Editor Layout

Most Power BI users only ever use a handful of buttons in the Power Query Editor — the ones they stumbled across in the first week. This lesson does a complete walkthrough of the entire interface: every ribbon tab, every column header control, every right-click menu, and the hidden panel options that significantly speed up your workflow once you know they exist.

The Home Tab

The Home tab contains the actions you use most often — loading, refreshing, managing queries, and the most common row and column operations. It is divided into groups that reflect the typical workflow order.

The Transform Tab

The Transform tab contains operations that modify existing columns in place — changing values, splitting text, extracting parts of dates, transposing the table, and more. Every action here modifies the currently selected column.

The Add Column Tab

The Add Column tab looks almost identical to the Transform tab — but there is one critical difference. Transform modifies the selected column in place. Add Column always creates a brand new column while leaving the original untouched. Use Add Column when you want to keep the original values alongside the derived ones.

The View Tab

The View tab controls what panels are visible and provides access to the Advanced Editor — where you can read and edit the full M code of any query. Most users ignore this tab entirely, which means they miss several tools that make working in the editor significantly faster.

Column Header Controls

Most of the actions beginners hunt for in the ribbon are available faster by interacting directly with the column headers. The column header area has three distinct interactive zones that most users never discover.

Right-Click Menus

Right-clicking in different areas of the editor reveals context menus packed with actions. Knowing what each right-click target offers saves enormous time — most of these actions are faster than hunting through the ribbon tabs.

Duplicate vs Reference — A Critical Distinction

Right-clicking a query in the Queries pane gives you two options that look similar but behave very differently. Getting these wrong is one of the most common causes of slow Power BI files.

DUPLICATE query:
  Creates a fully independent copy of the query.
  It re-runs the source connection and all steps independently.
  The copy has NO link to the original.
  If the original query is modified, the duplicate is unaffected.

  Use when:
    You want a separate table with different transformations
    applied to the same source, and both tables need to
    load into the model independently.

  Cost: reads the data source TWICE on every refresh.
  For large databases — expensive.

─────────────────────────────────────────────────────

REFERENCE query:
  Creates a new query that uses the ORIGINAL query's output
  as its starting point. It does not re-read the source.
  The source is read once; the reference query picks up
  from where the original left off.

  Use when:
    You want to create a staging query (clean the raw data)
    and then create separate final queries for Orders, Returns,
    Cancelled — all branching from the same cleaned source.

  Cost: source is read ONCE regardless of how many
  reference queries branch from it. Much more efficient.

─────────────────────────────────────────────────────

PATTERN — staging query with references:

  RawOrders          ← reads the source (loaded: disabled)
       │
       ├── Orders    ← reference, filters Status != Cancelled
       ├── Returns   ← reference, filters Status = Returned
       └── Cancelled ← reference, filters Status = Cancelled

  Source is read once. Three clean tables in the model.

Practice

Lesson Quiz

Next up — Lesson 18 covers Applied Steps in depth — how to reorder, rename, edit, insert steps mid-sequence, and what happens when a step breaks because of a change earlier in the chain.