Forum Discussion
Why DataLake over OneLake after adding new schema is not appearing in semantic model?
I agree with anilelmastasi here. as Fabric uses an asynchronous metadata refresh mechanism for Lakehouse objects. This means:
- When new files or schemas are added to the Lakehouse, Fabric updates its internal metadata catalogs in the background, not instantly.
- The Lakehouse UI may show updated files immediately, but the semantic model relies on metadata services that may still be catching up.
- When you click 'Refresh' in the semantic model, it pulls from that internal metadata catalog—not directly from the lake folder structure.
As a result, there can be a delay before the semantic model becomes aware of new schemas, even though the Lakehouse has already refreshed. some generic suggested actions are:
- Closing and reopening the semantic model
- Re-entering the “Edit tables” view
- Refreshing the entire Lakehouse again
- Waiting a few minutes
These actions don’t force a metadata refresh, but they may coincide with the background refresh completing.
Thanks,
Prashanth
Hi jaryszek,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
anilelmastasi, thanks for your prompt response
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support
Hello,
not it is not working for me. What Microsoft advices?
Best,
JacekI agree with anilelmastasi here. as Fabric uses an asynchronous metadata refresh mechanism for Lakehouse objects. This means:
- When new files or schemas are added to the Lakehouse, Fabric updates its internal metadata catalogs in the background, not instantly.
- The Lakehouse UI may show updated files immediately, but the semantic model relies on metadata services that may still be catching up.
- When you click 'Refresh' in the semantic model, it pulls from that internal metadata catalog—not directly from the lake folder structure.
As a result, there can be a delay before the semantic model becomes aware of new schemas, even though the Lakehouse has already refreshed. some generic suggested actions are:
- Closing and reopening the semantic model
- Re-entering the “Edit tables” view
- Refreshing the entire Lakehouse again
- Waiting a few minutes
These actions don’t force a metadata refresh, but they may coincide with the background refresh completing.
Thanks,
Prashanth
