Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Solved! Go to Solution.
Hi @dhruv_-_ ,
Try these before rebuilding to fix the issue.
1. clear file-specific cache.
File → Options → Current File → DirectQuery → Clear cache
Restart again.
2. Disable SQL Server folding cache
Go to:
File → Options → Global → Preview Features
Disable:
Improved model metadata
DirectQuery query reduction (if enabled)
Restart Power BI.
3. In Model View, for each affected table:
Select table,
Click Refresh in the Properties pane (this is a metadata refresh, not data refresh)
OR
Remove one column and add it back (forces schema reload).
4. In Model View, for each affected table:
Select table
Click Refresh in the Properties pane (this is a metadata refresh, not data refresh)
OR
Remove one column and add it back (forces schema reload).
5. Ensure all machines use the same Power BI Desktop version
Some versions had DirectQuery metadata bugs.
If my response as resolved your issue please mark it as solution and give kudos.
Hi @dhruv_-_
Thank you for reaching out to the Microsoft Fabric Forum Community.
@Kedar_Pande @Anonymous @kushanNa @Praful_Potphode Thanks for the inputs.
I hope the information provided by users was helpful. If you still have questions, please don't hesitate to reach out to the community.
Hi @dhruv_-_
Hope everything’s going smoothly on your end. I wanted to check if the issue got sorted. if you have any other issues please reach community.
hi @dhruv_-_
try changing the column name to something unique and then try.If this works, then there could be chances that you have renamed the column directly in desktop and its conflicting with it.
another option you can try is uncheck Enable Data load option in power query and close and apply.this will remove the table from desktop.then again check the Enable Data load option in power query and close and apply.
Please give kudos or mark it as solution once confirmed.
Thanks and Regards,
Praful
Hi @dhruv_-_
If you are using SELECT * try to do this ? https://www.reddit.com/r/excel/comments/epkj91/power_query_sql_error_but_no_changes_to_the_sql/
Hi @dhruv_-_ ,
Try these before rebuilding to fix the issue.
1. clear file-specific cache.
File → Options → Current File → DirectQuery → Clear cache
Restart again.
2. Disable SQL Server folding cache
Go to:
File → Options → Global → Preview Features
Disable:
Improved model metadata
DirectQuery query reduction (if enabled)
Restart Power BI.
3. In Model View, for each affected table:
Select table,
Click Refresh in the Properties pane (this is a metadata refresh, not data refresh)
OR
Remove one column and add it back (forces schema reload).
4. In Model View, for each affected table:
Select table
Click Refresh in the Properties pane (this is a metadata refresh, not data refresh)
OR
Remove one column and add it back (forces schema reload).
5. Ensure all machines use the same Power BI Desktop version
Some versions had DirectQuery metadata bugs.
If my response as resolved your issue please mark it as solution and give kudos.
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 23 | |
| 23 | |
| 21 | |
| 17 | |
| 13 |
| User | Count |
|---|---|
| 58 | |
| 51 | |
| 39 | |
| 29 | |
| 24 |