Forum Discussion
Interesting bug: renamed a table using Edit Query, made a few minor tweaks, and it went "missing"
Hi,
From your description, this appears to be related to how Power Query tracks query metadata during the Apply Changes process.
When you rename a query and make additional transformations in the same editing session, Power BI can occasionally retain a reference to the original query name in its dependency graph or pending changes. As a result, Apply Changes may still attempt to load the old table name, even though the preview displays the renamed query correctly.
A few things you can try:
Rename the query first, apply the changes, and then make any additional transformations (as you've already found works reliably).
Check whether any other queries, parameters, or disabled-load queries still reference the original table name.
Open View → Query Dependencies in Power Query to verify there are no lingering references to the old query.
If you're using incremental refresh, calculated tables, or relationships, confirm they aren't still pointing to the original query name.
Since the preview works correctly but Apply Changes fails, this may be a product bug rather than an issue with your query logic.
If you can reproduce it consistently with a simple example, I'd recommend reporting it through the Fabric/Power BI Issues forum or opening a Microsoft Support ticket. A reproducible sample will help determine whether this is a regression in the current Desktop release.
Has anyone else experienced the same behavior when renaming a query and making additional edits before applying the changes?
If you found this reply helpful, please consider giving it a Kudos. If it helps resolve your issue, marking it as the Accepted Solution will help others encountering the same behavior.
Hi SevsBo
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Thank you.
Hi,
From your description, this appears to be related to how Power Query tracks query metadata during the Apply Changes process.
When you rename a query and make additional transformations in the same editing session, Power BI can occasionally retain a reference to the original query name in its dependency graph or pending changes. As a result, Apply Changes may still attempt to load the old table name, even though the preview displays the renamed query correctly.
A few things you can try:
Rename the query first, apply the changes, and then make any additional transformations (as you've already found works reliably).
Check whether any other queries, parameters, or disabled-load queries still reference the original table name.
Open View → Query Dependencies in Power Query to verify there are no lingering references to the old query.
If you're using incremental refresh, calculated tables, or relationships, confirm they aren't still pointing to the original query name.
Since the preview works correctly but Apply Changes fails, this may be a product bug rather than an issue with your query logic.
If you can reproduce it consistently with a simple example, I'd recommend reporting it through the Fabric/Power BI Issues forum or opening a Microsoft Support ticket. A reproducible sample will help determine whether this is a regression in the current Desktop release.
Has anyone else experienced the same behavior when renaming a query and making additional edits before applying the changes?
If you found this reply helpful, please consider giving it a Kudos. If it helps resolve your issue, marking it as the Accepted Solution will help others encountering the same behavior.