Forum Discussion
Lakehouse Table Mapping Unidentified
I have a lakehouse that mirrors my production lakehouse. I have had no issue with the tables in the past but just this last week I received an error on my mirrored lakehouse: "Unable to identify these objects as tables or views. To keep these objects in the lakehouse, move them to Files" I have tried to move the tables to files and reconvert them to tables but it does not allow me to convert to file. I get the error: "Unable to move all unidentied items to Files". I am unsure on what to do to get these tables to start working again. Any suggestions? My next step if I am unable to figure this out is to recreate the lakehouse and remirror the data. I would prefer to avoid this as I have multiple reports that feed off this lakehouse so would like to resolve this if at all possible.
Hello JDay98
The issue with schema shortcuts is typically caused by:
- A corrupted or partially synchronised schema metadata file
- Modifications to the underlying Delta transaction log at the source
- Desynchronisation of shortcuts following schema evolution
- Inconsistent metadata within the mirrored lakehouse
Before addressing your mirrored lakehouse, please ensure the source is in good health.
Within your production lakehouse, confirm that /Tables exists and contains the *_delta_log:
Fabric shortcuts may have become outdated.
To refresh:
- Select the relevant schema shortcut
- Click Refresh
If the refresh is unsuccessful, it is likely due to metadata corruption in either the shortcut or the source.
From the mirrored lakehouse:
- Go to SQL Endpoint → Refresh
- Navigate to Tables view → Refresh
- If the problematic table displays a warning, select “Remove from SQL endpoint”
This action removes only the metadata and does not affect the actual data.
3 Replies
Hello JDay98
The issue with schema shortcuts is typically caused by:
- A corrupted or partially synchronised schema metadata file
- Modifications to the underlying Delta transaction log at the source
- Desynchronisation of shortcuts following schema evolution
- Inconsistent metadata within the mirrored lakehouse
Before addressing your mirrored lakehouse, please ensure the source is in good health.
Within your production lakehouse, confirm that /Tables exists and contains the *_delta_log:
Fabric shortcuts may have become outdated.
To refresh:
- Select the relevant schema shortcut
- Click Refresh
If the refresh is unsuccessful, it is likely due to metadata corruption in either the shortcut or the source.
From the mirrored lakehouse:
- Go to SQL Endpoint → Refresh
- Navigate to Tables view → Refresh
- If the problematic table displays a warning, select “Remove from SQL endpoint”
This action removes only the metadata and does not affect the actual data.
Hi JDay98,
Thank you for reaching out to Microsoft Fabric Community.
Thank you deborshi_nag for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
