Forum Discussion
Deployment Pipeline does not rebind Direct Lake semantic model to target Warehouse
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!
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!
Super UserHello seblopezarteta, you are likely hitting one of the limitations of Fabric Deployment pipelines related to Semantic models. Please check this article for detailed list of Semantic model support limitations:
The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
Specifically, the data source connection is not automatically changed in a Semantic model when it's deployed to another workspace. To make it happen you need to configure a deployment data source rule that will replace the data source connection. Read more about this here: The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn.
You can configure a deployment rule in the destination deployment stage, i.e. Test, only AFTER you deploy a Semantic model at least once. When you configure a rule, you can choose specific values related to the Warehouse SQL endpoint from the list of available. Keep in mind, that if you want to point your Semantic model to another Warehouse it must exist already before you can choose it and, of course, it has to have exactly the same schema.
Hope this information helps with your issue. If so, consider giving this answer kudos and mark as a solution for the benefit of other community members.
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!
Hi seblopezarteta ,
Glad to know the issue has been resolved with the workaroud.
We really appreciate your efforts and for letting us know the update on the issue.
Please continue using fabric community forum for your further assistance.
Regards
davidwarner344Advocate II
Glad you found a workaround! Using Tabular Editor to update the Shared Expression is a solid approach when deployment rules aren't available with Direct Lake. Thanks for sharing the solution it'll likely help others who run into the same limitation.