Forum Discussion
error that column doesn't exist when it does
- 10 months ago
Thank you. This is basically all the steps I had taken. I tried a second time and it worked. Basically, what worked was starting from scratch, which isn't really a solution. I wonder if anyone has discovered a reason for this occurring.
Hi lauriedata
I encountered the same issue, and here’s what worked for me:
The problem happens because Power BI keeps a cached reference to the old table, even after deletion and re-import. Any relationships, measures, or visuals that pointed to the old table can cause the “field doesn’t exist in the current context” error.
Steps to fix it:
Delete the problematic table completely from the model.
Clear the cache:
Go to File → Options and settings → Options → Data Load
Click Clear cache and restart Power BI.
Re-import the table but give it a new temporary name (e.g., TableName_New).
Check and remove broken relationships or measures that referenced the old table.
Rebuild your visuals from scratch if needed.
This completely resets the metadata and solved the issue for me.
Hope this helps!
- lauriedata10 months agoResolver I
Thank you. This is basically all the steps I had taken. I tried a second time and it worked. Basically, what worked was starting from scratch, which isn't really a solution. I wonder if anyone has discovered a reason for this occurring.