Forum Discussion
undefined
Hi lolsen1601,
Thanks for reaching out to the Microsoft fabric community forum.
From what you've described, it sounds like the table in your Lakehouse was deleted, but the metadata or link to that table still exists on the Data Warehouse side. When that happens, the system might still "remember" the table, even though the actual data or structure is gone which could explain why you're seeing issues or inconsistencies when trying to drop it.
Here are a few things you can try to solve your issue :
* Check if the table still appears in the Data Warehouse metadata catalog. You can run a query like "SHOW TABLES" or check "INFORMATION_SCHEMA.TABLES" to confirm whether the table is still listed. If it’s there, you may need to explicitly drop it using "DROP TABLE IF EXISTS [table_name]".
* If you used a shortcut to connect the Lakehouse table to the Data Warehouse, make sure that shortcut has also been removed from the Lakehouse. Sometimes the shortcut metadata lingers even after the table itself is deleted.
* If the table doesn’t appear anywhere but is still causing issues, there may be dependent views, pipelines, or reports referencing it. You may want to review any downstream objects that could still be calling this table.
* Refreshing or syncing the schema can also help clean up any stale references, especially if the metadata hasn’t updated automatically.
If you've already tried all of the above and are still hitting a wall, feel free to share any error messages you're seeing or the steps you've taken so far
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi lolsen1601,
Thanks for reaching out to the Microsoft fabric community forum.
From what you've described, it sounds like the table in your Lakehouse was deleted, but the metadata or link to that table still exists on the Data Warehouse side. When that happens, the system might still "remember" the table, even though the actual data or structure is gone which could explain why you're seeing issues or inconsistencies when trying to drop it.
Here are a few things you can try to solve your issue :
* Check if the table still appears in the Data Warehouse metadata catalog. You can run a query like "SHOW TABLES" or check "INFORMATION_SCHEMA.TABLES" to confirm whether the table is still listed. If it’s there, you may need to explicitly drop it using "DROP TABLE IF EXISTS [table_name]".
* If you used a shortcut to connect the Lakehouse table to the Data Warehouse, make sure that shortcut has also been removed from the Lakehouse. Sometimes the shortcut metadata lingers even after the table itself is deleted.
* If the table doesn’t appear anywhere but is still causing issues, there may be dependent views, pipelines, or reports referencing it. You may want to review any downstream objects that could still be calling this table.
* Refreshing or syncing the schema can also help clean up any stale references, especially if the metadata hasn’t updated automatically.
If you've already tried all of the above and are still hitting a wall, feel free to share any error messages you're seeing or the steps you've taken so far
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi lolsen1601 ,
That “undefined” error usually pops up when the UI fails to load certain metadata—especially around stored procedures, functions, or views. A few things you can try:
- Refresh the browser or close and reopen the tab. Sometimes it’s just a temporary glitch.
- Try a different browser or incognito mode to rule out cache issues.
- If you're using Azure Data Studio or SSMS, check if the objects show up there. Some users have reported that even when the Fabric UI fails, the objects are still accessible via external tools.
- If the issue is with Lakehouse, sometimes new tables or files appear under the “Unidentified” section temporarily while they’re being processed. They usually move to the correct folder after a bit.
If none of that helps, it might be a backend issue—worth raising a support ticket if it persists.
Hope this helps!
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.
Hi lolsen1601,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.Hi lolsen1601,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.
Thank you.Hi lolsen1601,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
