Forum Discussion
column deleted but column exists
so basically as you can see from the above pictures that it shows it is pointing to a deleted column but the column exists, so could you please help with the error.
Hi zamsam6931 ,
Thank you for reaching out to the Microsoft Community Forum.
Hi BITomS , grazitti_sapna , Thank you for your response.
Hi zamsam6931
This is a metadata cache issue or a model corruption issue that's fairly common when:
The column was deleted and then re-added with the same name. The data source was changed or refreshed and Power BI didn't update internal relationships correctly. Manual editing of relationships or column names caused a mismatch.
Please try these steps to fix the issue:
1. Remove and Recreate the Relationship
Even though you see the column, Power BI internally thinks it's broken.
Go to Model View. Delete the relationship between sale_order_table[team_id] and Salesteam_Bridge[team_id]. Recreate the relationship manually using the "Manage Relationships" dialog, or by dragging and dropping.
Make sure to confirm the data types match exactly.2. Refresh the Entire Model
Go to Home > Refresh to fully reload the data. This often forces Power BI to revalidate column references.
3. Rename the Column Temporarily
If the issue persists, Temporarily rename the team_id column in Salesteam_Bridge to something else.
Save and close Power BI. Reopen Power BI. Rename it back to team_id. Rebuild the relationship. This forces Power BI to rebuild the metadata cache.
4. Check for Duplicate or Hidden Models
In some cases, Power BI Desktop may hold onto ghost versions of tables especially if you are using DirectQuery or importing from multiple sources.
Open Model view and check if there’s a hidden or duplicate Salesteam_Bridge or shadow copy. Also, check Transform Data (Power Query) to verify that team_id exists and isn't renamed/removed in the applied steps.
5. Clear Cache and Reboot
Power BI might have corrupted cache:
Go to File > Options and Settings > Options > Data Load > Clear Cache. Restart Power BI.
If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.
Thank you
6 Replies
Hi zamsam6931 ,
Thank you for reaching out to the Microsoft Community Forum.
Hi BITomS , grazitti_sapna , Thank you for your response.
Hi zamsam6931
This is a metadata cache issue or a model corruption issue that's fairly common when:
The column was deleted and then re-added with the same name. The data source was changed or refreshed and Power BI didn't update internal relationships correctly. Manual editing of relationships or column names caused a mismatch.
Please try these steps to fix the issue:
1. Remove and Recreate the Relationship
Even though you see the column, Power BI internally thinks it's broken.
Go to Model View. Delete the relationship between sale_order_table[team_id] and Salesteam_Bridge[team_id]. Recreate the relationship manually using the "Manage Relationships" dialog, or by dragging and dropping.
Make sure to confirm the data types match exactly.2. Refresh the Entire Model
Go to Home > Refresh to fully reload the data. This often forces Power BI to revalidate column references.
3. Rename the Column Temporarily
If the issue persists, Temporarily rename the team_id column in Salesteam_Bridge to something else.
Save and close Power BI. Reopen Power BI. Rename it back to team_id. Rebuild the relationship. This forces Power BI to rebuild the metadata cache.
4. Check for Duplicate or Hidden Models
In some cases, Power BI Desktop may hold onto ghost versions of tables especially if you are using DirectQuery or importing from multiple sources.
Open Model view and check if there’s a hidden or duplicate Salesteam_Bridge or shadow copy. Also, check Transform Data (Power Query) to verify that team_id exists and isn't renamed/removed in the applied steps.
5. Clear Cache and Reboot
Power BI might have corrupted cache:
Go to File > Options and Settings > Options > Data Load > Clear Cache. Restart Power BI.
If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.
Thank you
Hi zamsam6931 ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Thank you.
Hi @zamsam6931 ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Thank you.
Hi zamsam6931 ,
Have you tried deleting the relationship, refreshing the model and then re-applying the relationship?
This might diagnose if any schema changes have been made that may be causing the error.
Hi zamsam6931
1.Delete the broken relationship manually
Then recreate the relationship fresh using the current columns.
2. Changes in Power Query not reflected in the model
Sometimes changes in Power Query (like removing and re-adding columns) don't fully update in the data model until it's refreshed.
Click on Close and apply after changes.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
