How to Change Data Source Location in Power BI

Few things interrupt your data visualization flow more than Power BI suddenly throwing an error because a file simply moved from one folder to another. One moment your dashboard is working perfectly, and the next you’re staring at a screen full of broken visuals after a routine file cleanup. This article will show you exactly how to change the data source location for local files like Excel or CSVs, getting your report fixed in minutes without having to rebuild it from scratch.

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 Does Power BI Show an Error When You Move a File?

When you import data from a local file, such as an Excel workbook or a CSV file on your computer, Power BI saves the exact file path. Think of it as a specific, physical address. For example, it might record the location as C:\Users\YourName\Documents\MonthlyReports\Sales_April.xlsx.

Power BI relies on this static path to find and refresh your data. If you move, rename, or delete that file - or even just reorganize the folder it lives in - the address becomes incorrect. The next time you try to refresh your report, Power BI follows the old path, finds an empty lot where a house (your data) used to be, and displays an error message. It’s the dreaded "source not found" problem, and it's thankfully easy to correct.

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 1: Locate the Broken Data Source

First, you need to confirm which data source is causing the problem. Usually, Power BI makes this clear with a yellow error banner after a failed refresh, often saying "Data source error: Could not find a part of the path..." or something similar. To pinpoint the issue, you’ll head to the Power Query Editor.

1. On the Home ribbon in Power BI Desktop, click Transform Data. This opens the Power Query Editor, which is the engine room for all of your data connections.
2. In the Queries pane on the left, look for any query with a small yellow warning icon (a triangle with an exclamation mark). This is your broken connection.
3. Select the query that has the error. Now, look at the Applied Steps pane on the right. The issue almost always lies in the very first step, named Source.
4. Click the small gear icon next to the Source step. A dialog box will appear, showing you the exact file path that Power BI is trying to use. Now you've confirmed the old location and you’re ready to update it.

Step 2: The Quickest Fix for a Single File

If you're only dealing with one or two moved files, this simple method inside the Power Query Editor is the fastest way to get your report back on track.

Changing the Source Directly

Follow a simple, direct path to fix the location for a broken query. By updating the source setting for a single file, you'll immediately fix the connection, get your visual back up and running, and refresh your dashboard with the correct info:

• 1. Open the Source Settings: With your broken query selected, navigate to the Applied Steps and click the gear icon next to Source.
• 2. Browse for the New File: In the dialog box (which will vary slightly depending on if you're using Excel, CSV, or another file type), you will see the incorrect file path displayed. Click the Browse... button.
• 3. Select the New Location: Navigate through your computer’s folder structure to find the new location of your data file. Select the file and click Open.
• 4. Confirm the Change: The file path in the dialog box will now be updated. Click OK.
• 5. Close & Apply: The data preview in Power Query Editor should now load successfully. Click the Close & Apply button in the top-left corner to save your changes and return to your main report view. Your visuals should now update and load correctly.

More Control with the Advanced Editor

Sometimes you might need to make more direct changes or simply want to see the underlying M code that Power Query generates. That's where the Advanced Editor comes in handy. It offers a more "under the hood" approach to changing your file path, letting you edit the source location manually.

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

Manually Editing the M Code

1. In the Power Query Editor, make sure the correct query is selected.
2. Click on the Advanced Editor button, which can be found in either the Home or View tab.
3. A new window will open displaying the M code for your query. The file path is always located in one of the first lines, often within a function like File.Contents(). It will look something like this:

let
    Source = Excel.Workbook(File.Contents("C:\OldPath\Reports\SalesData.xlsx"), null, true)
in
    Source

1. Carefully edit the file path inside the quotation marks to point to the new location. Remember to include the full file name and extension. Be mindful of backslashes.
2. Here is the updated example:

let
    Source = Excel.Workbook(File.Contents("C:\Users\YourName\NewReports\Master\SalesData.xlsx"), null, true)
in
    Source

1. Click Done. If the path is correct, the query preview will load your data.
2. Click Close & Apply to save the changes.

Beat The Problem Before It Starts: Using Parameters

If you're connecting to multiple files within the same folder, updating each one individually is tedious and prone to error. A far more robust and efficient solution is to use parameters. By creating a parameter for your folder path, you can define the location once. If you ever move the entire folder again, you only have to update the one parameter, and every query referencing it will automatically update.

1. Create a Folder Path Parameter

First, we need to create a parameter that will hold the text value of our folder path.

1. In the Power Query Editor, click Manage Parameters on the Home ribbon, then select New Parameter.
2. A configuration window will appear. Fill it out as follows:

For example: C:\Users\You\Documents\FinalReports\

1. Click OK. You'll now see your new parameter listed in the queries pane.

2. Apply the Parameter to Your Queries

Next, we need to instruct our existing queries to use this new parameter instead of a hardcoded file path.

1. Select one of the queries that uses a file from that folder.
2. Open the Advanced Editor.
3. Look for the original Source line, which contains the hardcoded path:

Source = Csv.Document(File.Contents("C:\Your\OldPath\2024_Sales.csv"), [Delimiter=",", Columns=15, Encoding=1252, QuoteStyle=QuoteStyle.None]),

1. Now, modify that line to combine your parameter and the filename. In M language, you can combine text values using an ampersand (&). The modified line should look like this:

Source = Csv.Document(File.Contents(p_DataSourceFolder & "2024_Sales.csv"), [Delimiter=",", Columns=15, Encoding=1252, QuoteStyle=QuoteStyle.None]),

1. Click Done. Your query is now dynamic!
2. Repeat this process for all other queries that retrieve files from that same folder.

From this point on, if that entire folder of files moves again, all you have to do is click Manage Parameters, update the Current Value of your p_DataSourceFolder parameter, and all your reports will work again instantly. No more changing one by one!

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

Best Practices to Avoid Data Source Errors

While fixing broken data sources is easy, avoiding the problem altogether is even better. Here are a few best practices to make your Power BI reports more stable:

• Use Cloud Storage: Whenever possible, store your data files in OneDrive or SharePoint. When connecting to files here, Power BI uses a URL instead of a local file path. This ensures that anyone with access on your team can refresh the report without issue, as the data source isn't tied to one person's computer.
• Centralize Your Data: Create a dedicated, well-organized folder structure for all a project's data sources. Avoid leaving files scattered across your Desktop, Downloads folder, and Documents folders. This makes management and updating paths easier in the future.
• Communicate With Your Team: If you're working on a shared project, make sure everyone on the team knows where the data sources are available. This avoids unnecessary frustration and workload when critical files or folders are moved. Simple communication can prevent major workflow disruption.

Final Thoughts

Fixing a broken data source link in Power BI is a common hurdle, but it's easily solved once you know where to look. Whether you're quickly redirecting a single file path through the editor, taking more control in the Advanced Editor, or proactively setting up dynamic parameters to future-proof your reports, you can get your dashboards back online without needing to start from zero.

Ultimately, the goal is always to spend less time on tedious report maintenance and more time analyzing data. At Graphed, we handle the annoying parts of data management, like connecting directly to your marketing and sales platforms and keeping everything in sync. Instead of struggling with broken source paths manually, you can focus on what you need to.