Forum Discussion
Semantic Model Breaks After DirectQuery to Direct Lake Migration Refresh
Hi,
We followed a similar approach for migration using the Semantic Link Labs notebook:
semantic-link-labs/notebooks/Migration to Direct Lake.ipynb at main · microsoft/semantic-link-labs · GitHub
The migration was executed via notebook, and all the source tables are available in the Lakehouse. Also, the required users have been granted Contributor access on the workspace.
Despite this setup, we’re still seeing the semantic model break post migration from DirectQuery to Direct Lake.
Would be helpful to understand if there are any additional configurations or limitations we might be missing—especially around permissions, table compatibility, or model refresh behavior in Direct Lake.
Thanks
Thank you for reaching out to the Microsoft Fabric Forum Community.
Tamanchu Thanks for the inputs.
Since the tables are available and permissions seem correct, the issue may be related to how the model reconnects to the Direct Lake tables after a refresh. It's also possible that KPIs and calculated columns aren't fully carried over during the migration process.
As a next step, can you please check whether the missing relationships are limited to specific tables and confirm if KPIs and calculated columns are supported in Direct Lake after migration.
If the issue still persists after these checks, the best approach would be to open a Microsoft support ticket Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn, as a successful migration and refresh shouldn’t normally cause the model to break.
If there are any deviations from your expectation please let us know we are happy to address.
Thanks.
Hi Shreya_Barhate
I hope you’ve submitted the support ticket. If you’ve received a solution, please share it here so it can help others who encounter a similar issue.