New bug confirmed: Renaming a table that is referenced by another query turns off "Enable Load"

[mike_honey]

Alex from the Power BI Product team has confirmed that this is a new bug, and they are working on a fix.  In the meantime, beware of renaming tables in your semantic model, without a recent save point to roll back to.

Renaming a table that is referenced by another query turns off "Enable Load", effectively deleting the source table:
https://www.reddit.com/r/PowerBI/comments/1ksmqnh/bug_renaming_a_table_that_is_referenced_by/

[v-nmadadi-msft · Accepted solution]

Hi  @mike_honey ,

I have been keeping an eye on Known issue document and other Microsoft document related to the bug you have encountered but there have not been any updates so far regarding them.
So as to get faster updates we encourage you to open a support ticket here:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

For now we are closing this thread, should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread or reopen this thread. We’ll be happy to help.

Thank you for your understanding and participation.

[mike_honey · Accepted solution]

Support were in contact, and this issue has been resolved in the July 2025 update (version 2.145.1105.0 64-bit (July 2025)).
I have tested using my repro and the original behaviour has been restored, i.e. we can safely rename tables again.

[v-nmadadi-msft · Accepted solution]

Hi  @mike_honey ,

I have been keeping an eye on Known issue document and other Microsoft document related to the bug you have encountered but there have not been any updates so far regarding them.
So as to get faster updates we encourage you to open a support ticket here:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

For now we are closing this thread, should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread or reopen this thread. We’ll be happy to help.

Thank you for your understanding and participation.

[mike_honey]

I've started a support case for this: 2506230030005715.

[v-nmadadi-msft]

Hi @mike_honey ,
Thanks for reaching out to the Microsoft fabric community forum

We really appreciate your efforts and for letting us know about the bug.
As soon as Microsoft provides an update about it, I will post about it in this post.
In the meantime please continue using fabric community forum for your further assistance.

Thank you

[burakkaragoz]

Hi @mike_honey ,

Thanks for sharing this. I actually ran into the same issue last week and couldn’t figure out what was going on until I saw this post.

It’s definitely a tricky one, especially when you're working with layered queries and don’t realize the downstream impact of a rename. Good call on the rollback tip — saving before renaming anything in the model is a must for now.

Hope the fix rolls out soon. Meanwhile, I’ll probably stick to duplicating tables before renaming just to be safe.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI