logo
search
Power Query Problems

How to Fix Power Query Not Importing New Excel Columns

Muhammad TalhaMuhammad Talha Oct 16, 2026 869 views

Question details

Users are unable to see newly added columns from their source Excel files after refreshing their Power Query.

How to Fix Power Query Not Importing New Excel Columns
Product
Microsoft Excel
Device & OS
not provided
Scenario
Refreshing a Power Query to include newly added columns from an existing Excel data source.
Observed behavior
The newly added columns do not appear in the final Power Query output, often because they are blocked by hardcoded column lists in the "Changed Type" step or other preceding transformations.
Before you start

Before modifying your query steps, ensure that the source Excel file has been saved with the newly added columns and that there are no hidden trailing spaces or typos in the new column headers.

Solution 1Recommended

Remove and Recreate the Changed Type Step

The easiest way to fix this issue is by deleting the hardcoded "Changed Type" step and letting Power Query detect the new columns naturally.

Power Query automatically creates a "Changed Type" step when importing data. This step hardcodes the names of all existing columns. If a new column is added to the source, this step ignores it because it is not in the hardcoded list.

1
Open Power Query Editor

Go to the Data tab in Excel and click on "Queries & Connections". Double-click your query to open the Power Query Editor.

2
Locate the Applied Steps

On the right side of the screen, look at the "Applied Steps" pane.

3
Delete the Changed Type Step

Find the step named "Changed Type" (or similar) and click the "X" icon next to it to delete it temporarily.

4
Refresh and Reapply

Click "Refresh Preview" to allow Power Query to pull in the new columns. Then, select all columns (Ctrl + A), navigate to the "Transform" tab, and click "Detect Data Type" to recreate the step with all columns included.

Remove and Recreate the Changed Type Step
Pro Tip: You can turn off automatic data type detection in Power Query Options (File > Options and settings > Query Options > Data Load) to prevent this from happening automatically in future queries.
Free Microsoft Office alternative

Easily Manage Your Spreadsheet Data with WPS Office

While advanced Power Query errors and hardcoded M-code steps can be frustrating in Microsoft Excel, WPS Office provides a lightweight, highly compatible alternative for everyday data analysis, filtering, and reporting without the heavy overhead.

100% compatible with Microsoft Excel (.xlsx, .xls, .csv) formats.Intuitive interface for seamless data sorting, filtering, and pivot table creation.Lightweight installation that runs smoothly on older and newer devices.Completely free alternative to expensive Microsoft Office subscriptions.
microsoft office alternative - wps office

Frequently Asked Questions

Why does the "Changed Type" step break my Power Query when source columns change?

The "Changed Type" step automatically hardcodes the exact names of all columns present at the time it was created. If new columns are added, they aren't in this hardcoded list and are subsequently ignored in the data type assignment. If an existing column is removed or renamed, the hardcoded step throws a "column not found" error.

How do I make my Power Query dynamic so it always imports new columns?

To keep queries dynamic, avoid using steps that hardcode column names, such as "Remove Other Columns" or the automatically generated "Changed Type". You can delete the "Changed Type" step entirely if strict data typing isn't necessary for your analysis, or apply data typing only to specific columns rather than the entire table.

I deleted the Changed Type step, but my new Excel column is still missing. What's wrong?

If the column is still missing, a different preceding step is likely filtering it out. Check for steps like "Removed Columns", "Kept First Rows", or check your source range. If you imported data from a static range (e.g., A1:D100) instead of a dynamic Excel Table, new columns outside that range won't be imported. Format your source data as an Excel Table (Ctrl+T) to fix this.