Power Query Problems

Fix Power Query Renaming and Disconnecting from Excel PivotTable

Steven ParkerSteven Parker Oct 28, 2026 868 views

Question details

The user needs to resolve an issue in Microsoft Excel 365 where a merged Power Query automatically changes its name, loses its connection to a PivotTable, and displays specific framework or path errors.

How to Fix Power Query Renaming and Disconnecting from PivotTables in Excel
Product
Microsoft Excel 365
Device & OS
not provided
Scenario
Refreshing merged Power Queries that are connected to SharePoint files or an OLAP cube.
Observed behavior
After repeated refreshes, the query renames itself with a suffix like (2), disconnects from the PivotTable, and triggers a 'Section1 query path does not exist' error. The Queries and Connections pane may also get stuck displaying 'Loading .NET Framework'.
Before you start

Always create a complete backup copy of your Excel workbook to prevent accidental data loss before deleting connections or troubleshooting Power Query paths.

Solution 1Recommended

Isolate the Issue Using a Local Excel File

Determine if the connection bug is caused by SharePoint or OLAP sources by testing the query refresh process with a simple local file.

Because this specific glitch occurs unpredictably with SharePoint files and OLAP cubes in Microsoft 365, narrowing down the source is a crucial first step.

1
Create a test workbook

Launch Microsoft Excel and open a new blank workbook to serve as your controlled testing environment.

2
Import local data

Navigate to the Data tab on the ribbon, click Get Data > From File > From Workbook, and select a locally saved Excel file instead of a cloud or SharePoint file.

3
Test the refresh cycle

Create a basic PivotTable connected to this new local query, then refresh the data multiple times to observe if the automatic renaming or disconnection still occurs.

Isolate the Issue Using a Local Excel File
Free Microsoft Office alternative

Experience Stable Spreadsheets with WPS Office

Dealing with unpredictable Microsoft 365 Power Query bugs can disrupt your workflow. WPS Office provides a free, lightweight, and highly compatible alternative for your spreadsheet needs. Enjoy a familiar interface without complex .NET Framework dependency issues, ensuring seamless data analysis and stress-free migration.

  1. 1. Download WPS Office: Visit the official WPS website to download the free installation package for your device.
  2. 2. Install the application: Run the setup file and follow the simple on-screen instructions to install WPS Office.
  3. 3. Open your spreadsheets: Launch WPS Spreadsheets and open your existing .xlsx files to resume your data analysis seamlessly.
Free and lightweight without heavy .NET Framework dependenciesFully compatible with Microsoft Excel formats (.xlsx, .csv)Familiar UI design ensures a zero learning curveRobust built-in data analysis tools for quick insights
microsoft office alternative - wps office

Frequently Asked Questions

Why does my Power Query automatically add a number like (2) to its name?

This usually happens when Excel detects a perceived naming conflict or briefly loses track of the original query connection during a refresh. This bug is particularly common in Microsoft 365 when syncing with external sources like SharePoint or OLAP cubes, causing Excel to duplicate the query name.

What does the 'Section1 query path does not exist' error mean in Excel?

This error signifies that Excel's internal data model has lost the reference map to your original Power Query. When the query improperly renames itself during a refresh cycle, the PivotTable pointing to the original name can no longer find the path, triggering the Section1 error.

How can I prevent Power Query from disconnecting from my PivotTable?

Because this is often tied to a Microsoft 365 version-specific bug involving cloud sources, you can mitigate it by saving the source files locally instead of on SharePoint. Additionally, ensuring your Office installation is fully updated or running an Online Repair may resolve background .NET Framework issues causing the disconnect.