Semantic Model Breaks After DirectQuery to Direct Lake Migration Refresh

Hi Shreya_Barhate

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.