Forum Discussion
Excel Power Query: editing unloaded query refreshes dependent queries
Hi all
There has been a change between version 2601 and 2602 on the Current channel which means that when editing a query in Power Query it will trigger a refresh for all dependent queries. This makes Power Query unusable for any complex queries or large data extraction.
Take the below example M code. SourceQuery is not loaded to the workbook or data model. LoadedQuery references SourceQuery and is loaded to the workbook.
Query: SourceQuery
let
Source = #table({"Col1"},{{"x"}})
in
Source
Query: LoadedQuery
let
Source = SourceQuery
in
Source
In version 2601 and previous versions, you could edit SourceQuery, 'close and load' Power Query and save your workbook almost instantly because no data was refreshed. In 2602 and later versions editing SourceQuery forces a refresh of LoadedQuery which can be very time consuming but more frustrating for all my complex/larger workbooks it triggers lots of refreshes which never finish and result in my having to end task on Excel (note: refreshing these queries takes less than 10 seconds). Doing an end task on all the mashup containers does not allow me to regain control of the Excel workbook. This means all changes to the workbook are lost. I have had to resort to using a VSCode extension to edit my Power Query without crashing Excel.
The builds I have tested are 2601 19628.20166 and 2602 19725.20190.
Are there any plans to rollback this change?
Other than rolling back my Outlook version or using VSCode are there any methods to edit my queries without crashing Excel?
It would also be helpful to understand why such a large change in functionality was not captured in the release notes. Per the release notes there were no changes to Excel in 2602, not even 'various fixes to functionality and performance'.
Many thanks, Andrew
1 Reply
- Olufemi7Steel Contributor
Hello ajlind25,
Based on your testing, this does appear to be a behavioral change introduced around Current Channel version 2602.
Previously, editing an unloaded staging query typically did not refresh dependent loaded queries during Close & Load. In newer builds, dependency evaluation appears to occur more aggressively.
I am not aware of any published Microsoft documentation confirming whether this is intentional or a regression.
A few things you can try:
- Disable background refresh in Query Properties
- Disable parallel loading under File > Options > Data
- Keep intermediate queries as Connection Only
- Temporarily disable downstream loads while editing staging queries
- Test Monthly Enterprise or Semi-Annual Enterprise Channel builds
I would also recommend submitting feedback with:
- exact build numbers
- repro steps
- whether the issue occurs in a new blank workbook
Current Channel release notes:
Microsoft 365 Current Channel release notes