All articles

Power Query

Append queries in Power BI: stack tables without losing rows

How to append queries in Power Query, what happens when column names don't match, and when a folder connection is the better choice.

9 November 2026·3 min read·Sources listed at the end

Sales, all storesStoreMonthSalesNorthJanuary41,250NorthFebruary38,900NorthMarch44,120SouthJanuary29,640SouthFebruary33,475SouthMarch31,080

Append queries stacks tables on top of each other. Use it when you have the same kind of data split across several tables, such as one sales file per month or one table per store. The result has the rows of all of them.

Append adds rows. If you want to add columns from another table by matching a key, you need merge queries.

How to append queries in Power BI

  1. In Power BI Desktop, select Transform data to open Power Query.
  2. Select the first query.
  3. On the Home tab, in the Combine group, select Append queries. Choose Append queries as new to create a separate table and keep the originals.
  4. Choose Two tables and pick the second table, or choose Three or more tables and add each one to the list.
  5. Select OK, then check the row count.

The row count of the result should equal the row counts of the sources added together. Checking this takes ten seconds and catches most mistakes.

How columns are matched

Append matches columns by name, not by position. That leads to the most common surprise:

Situation Result
Same names in both tables Rows stack cleanly
A column exists in only one table The column is kept, with null for rows from the other table
Sales in one, Revenue in the other Two separate columns, each half empty
Country and country Two separate columns, because names are case sensitive

So if your result has more columns than you expected, or a column full of null, a name doesn’t match. Rename the column in the source query, before the append step, and the problem disappears.

Check data types after appending

If a column is a number in one table and text in another, the appended column may end up with the type Any. Set the type on each source before the append, or add a Changed type step after it. A column left as Any can cause trouble once it reaches your report.

Keep track of where each row came from

After stacking, you can no longer tell which file or store a row came from. If that matters, add a custom column to each source first, for example Store = "North", and then append.

When to use a folder instead

Appending by hand is fine for two or three fixed tables. If a new file arrives every month, use the Folder connector:

  1. Select Get data > Folder and choose the folder.
  2. Select Combine & Transform Data.
  3. Pick a sample file and confirm the settings.

Power Query combines every file in the folder. Next month, drop the new file in and refresh, with no change to the query. The files must have the same structure, and it’s worth filtering out any other file types in the folder.

Turn off load for the source tables

After an append, your model may hold the combined table and all the original pieces. Those extras take up space and clutter the Data pane. Right-click each source query in Power Query and untick Enable load. The append still works, but only the final table reaches your model.

The M code behind it

Power Query writes this step for you:

= Table.Combine({January, February, March})

To add another table later, you can add its name to the list in the formula bar.

Sources

Practice it

Append and merge queries

Stack files from two stores, then bring in product details with a merge.

Open the lesson

Read next