How to Update Query in Power BI

When the underlying data source for your Power BI report changes, it can feel like everything breaks. A renamed column, a moved file, or a new data format can bring your dashboards to a halt. This article will show you how to navigate the Power BI Query Editor to quickly update your queries and get your reports back on track, without the headache.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Why Do You Need to Update Queries in Power BI?

Queries are the instructions Power BI follows to connect to your data and transform it into a clean, usable format. When the source data changes, the instructions no longer work. Think of it like a recipe. If an ingredient is suddenly different or missing, you need to adjust the recipe to get the right result.

Here are a few common reasons your queries might need an update:

• The file was moved. The monthly sales report you link to from a shared drive might have been moved to a new folder, breaking the file path connection.
• Column names were changed. The source Excel file now has a column named "Sales_Region" instead of just "Region," causing any steps that reference "Region" to fail.
• Data types are different. An API now returns a customer ID text ("ABC-123") instead of just a number ("123"), which can cause data type errors in your report.

Luckily, fixing these issues is usually a simple process once you know where to look. The solution nearly always lives inside the Power Query Editor.

Your Toolkit: The Power Query Editor

The Power Query Editor is the engine room of Power BI. It's where you perform all the data cleaning and preparation steps - the "Transform" part of "Extract, Transform, Load" (ETL). To open it, just click the Transform data button on the Home tab in Power BI Desktop.

Inside, there are a few key areas to know:

• Queries Pane (Left): A list of all the tables (queries) in your report.
• Data Preview (Center): A view of your data as it looks after each transformation step.
• Applied Steps Pane (Right): This is the most crucial part for our task. It lists every single transformation Power BI has applied to your data, in order. Each action you take - from connecting to the source to filtering rows to renaming columns - is recorded as a step here.

To update a query, you don’t have to start over. You just need to find the specific Applied Step that's broken and either edit it or fix the source information.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step-by-Step Guide to Updating Your Queries

Let's walk through some of the most common scenarios you'll face and how to troubleshoot them using the Applied Steps pane.

Scenario 1: The Data Source Path Has Changed

This is probably the most frequent issue. A finance team member saves the monthly CSV file in a new folder named "Q3 Reports" instead of "Q2 Reports," and now your report is showing an error because it can't find the file.

1. Open the Power Query Editor by clicking Transform data on the Home ribbon.
2. In the left-hand Queries pane, select the query that is failing.
3. In the Applied Steps pane on the right, find the very first step, which is almost always named Source.
4. Click the small gear icon to the right of the Source step.

A dialog box will appear, showing the current connection settings. For an Excel or CSV file, this box will contain the file path. Simply click Browse... and navigate to the new file location, select it, and click OK. The data preview will refresh, and your query will now be pulling from the new source. All subsequent steps will apply to this new data automatically.

Pro Tip: Use Parameters for File Paths

To avoid this problem in the future, you can use parameters to manage file paths. Instead of hard-coding the file path in the Source step, you can point it to a parameter. That way, if the path changes again, you only need to update the parameter's value in one place, and any query using that parameter will update instantly.

To create one, go to the Home tab in Power Query, click Manage Parameters > New Parameter. Give it a name like FilePath, set the Type to Text, and enter the folder path as the "Current Value." Then, in your query's Source step, edit the M code in the formula bar to reference this parameter instead of the static text path.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Scenario 2: Correcting a Transformation Step

Sometimes the source is correct, but one of your transformation steps is now wrong. Imagine you originally filtered your sales data to show only results from the "USA." Now, you need to include "Canada" as well.

1. In the Power Query Editor, select the relevant query.
2. Scan the Applied Steps pane for a step that looks like what you want to change. In this case, it’s likely named Filtered Rows.
3. Click the gear icon next to the "Filtered Rows" step.
4. The filtering dialog box will open, showing your original condition (e.g., Country equals USA). You can now modify this to include an "OR" condition for Canada or change the filter logic completely.
5. Once you click OK, the data preview will update to include the new data.

This same process works for almost any step. You can use the gear icon to adjust sorted columns, change the rules for replaced values, or modify how a column was split.

Scenario 3: Fixing a "Column Not Found" Error

You open your weekly report and see the dreaded error: "Expression.Error: The column '[Column Name]' of the table wasn't found." This typically happens when a column in your source file has been renamed. For example, "Customer Name" is now "Client_Name."

1. Open the Power Query Editor. The failing query will likely have an error icon next to it.
2. Select the query. In the Applied Steps pane, you'll see steps with yellow and red error indicators.
3. Click on the first step that shows an error. Look at the formula bar at the top of the window. A step that renames or references a column will contain M code, for example:
4. The error happens because the step is looking for "Customer Name," but that column no longer exists.

You have a few ways to fix this:

• Edit the M Code: The quickest fix is often to edit the M code directly in the formula bar. Just replace the old column name with the new one:
• Re-apply the Step: You can delete the failing step (by clicking the "X" next to it) and the one before it, then re-apply the transformation from the ribbon. For example, if your "Renamed Columns" step is failing, delete it, use the ribbon to rename the new "Client_Name" column, and Power Query will generate a new, correct applied step.
• Fix It at the Source (step): A better long-term solution is to sometimes go back to the source step. If your source is a database query, you might be able to edit the SQL statement there to use an alias, renaming "Client_Name" back to "Customer Name" as the data is pulled into Power BI.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Unlocking an Advanced Fix: The Advanced Editor

For more complex updates – say, a server name changed and it's referenced in 10 different places within a single query – the Advanced Editor is your best friend. With your query selected, click the Advanced Editor button on the Home tab. This opens a window showing the query's full M code script.

You can see all of your applied steps laid out here. This allows you to perform find-and-replace operations across the entire script. For example, you could press Ctrl+H to replace all instances of an old server name with a new one.

A brief word of caution: the Advanced Editor is powerful but unforgiving. A single typo can break the whole query. Before making major changes, it's a good practice to copy the original code and paste it into a text editor as a backup.

Final Thoughts

Updating queries in Power BI comes down to understanding the Applied Steps pane in the Power Query Editor. Whether you’re fixing a broken source path, modifying a filter, or correcting a changed column name, that ordered list of steps is where you will find the problem and apply the solution. Getting comfortable there moves you from being a report user to a report builder.

Manual reporting, whether in Power BI or spreadsheets, is often burdened by maintenance like this. At Graphed, we handle the data pipeline and analytics for you so you can focus on insights, not on fixing broken queries. Since we connect directly to your marketing and sales platforms like Google Analytics, Shopify, and Salesforce, you never have to worry about updating data sources. Instead, you can ask questions in plain English like, "compare my ad spend to revenue by campaign," and watch as a dashboard gets built for you in real time with live, continuously updated data.