Forum Discussion
Deployment Pipeline does not rebind Direct Lake semantic model to target Warehouse
- 3 months ago
Hi apturlov,
I wasn't able to update/create the deployment rule, guess it's because the SM connects to the WH via Direct Lake mode.
I finally did update the Shared Expression using Tabular Editor, pointing it to the Test WH. That worked as workaround to continue with the Test full deployment.
Thanks a lot anyway for your help!
Best!
- 3 months ago
Hi seblopezarteta,
This is expected. Directlake on OneLake models are not fully supported by deployment pipelines yet. I hope that one day soon they are.
For now my workaround is very similar to what you did, editing the deployed semantic model to point to the new lakehouse/warehouse. I use VS Code and Fabric Studio for this, but tabular editor works just as well.
THis limitation is outlined in the docs: The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
Though the docs say to use datasource rules to rebind them, that only works for directlake on SQL, not directlake on OneLake.
- 3 months ago
Hi tayloramy,
Thanks for your reply!
I also hope this will solved in a near future! In the meantime, we'll continue using the workaround, will have a look to you VSCode solution! Thanks for that!
Hi seblopezarteta,
This is expected. Directlake on OneLake models are not fully supported by deployment pipelines yet. I hope that one day soon they are.
For now my workaround is very similar to what you did, editing the deployed semantic model to point to the new lakehouse/warehouse. I use VS Code and Fabric Studio for this, but tabular editor works just as well.
THis limitation is outlined in the docs: The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
Though the docs say to use datasource rules to rebind them, that only works for directlake on SQL, not directlake on OneLake.
Hi tayloramy,
Thanks for your reply!
I also hope this will solved in a near future! In the meantime, we'll continue using the workaround, will have a look to you VSCode solution! Thanks for that!