Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hi, we are facing typical issue with Microsoft Fabric warehouse. We created a table and dropped (after deleting the data) but we still see the table in the schema (on the leftside under schema ancestor) and if we do a select command on that very specific table it was showing table or view doesnot exist. It is strange, is it something known issue, physically table deleted but on the user interface it is still visible (it causing very confusion). Is anyone face the same issue, please help us resolving the same.
Thanks.
Krishna.
Solved! Go to Solution.
Hi @ivamsikrishna,
This is a known UI behavior in Microsoft Fabric Warehouse. Even after a table is dropped, it may still show up in the schema explorer due to metadata caching in the UI. However, if you query the table and it returns "does not exist," then the table has been correctly dropped at the backend.
You can safely refresh the schema pane (right-click → Refresh) or reopen the warehouse tab to clear the UI cache. This doesn’t affect actual data operations and is just a temporary UI artifact.
Thanks,
Prashanth
Hi @ivamsikrishna,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @ivamsikrishna,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @ivamsikrishna ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
@ivamsikrishna As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @ivamsikrishna,
This is a known UI behavior in Microsoft Fabric Warehouse. Even after a table is dropped, it may still show up in the schema explorer due to metadata caching in the UI. However, if you query the table and it returns "does not exist," then the table has been correctly dropped at the backend.
You can safely refresh the schema pane (right-click → Refresh) or reopen the warehouse tab to clear the UI cache. This doesn’t affect actual data operations and is just a temporary UI artifact.
Thanks,
Prashanth
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
10 | |
4 | |
4 | |
3 | |
3 |