Thanks for the deployment explanation, how we can we change underlying DB connection if I am deploying Semantic model/Lakehouse from Dev to Test/Production?
Hi, thanks for sharing. I've tried to apply that. I understand there are still some limitations as the deployment pipelines doesn't work on Data Flow Gen 2. Moreover, I try to deploy a DWH where there are couples of views; which create the deployment of this DWH to fail. Do you know when will this be corrected?
There is a new Dataflow Gen 2 that was just released with CICD in it. idk if this means we have to recreate our old DF, I have not been able to play with this yet. I thought the DW migration with views was fixed... if not, soon
Thanks for the deployment explanation,
how we can we change underlying DB connection if I am deploying Semantic model/Lakehouse from Dev to Test/Production?
Hi, thanks for sharing. I've tried to apply that.
I understand there are still some limitations as the deployment pipelines doesn't work on Data Flow Gen 2.
Moreover, I try to deploy a DWH where there are couples of views; which create the deployment of this DWH to fail. Do you know when will this be corrected?
There is a new Dataflow Gen 2 that was just released with CICD in it. idk if this means we have to recreate our old DF, I have not been able to play with this yet.
I thought the DW migration with views was fixed... if not, soon
can you please tell how can I automate this in power bi
Today deployment pipelines in Fabric cannot be easily automated. If you want to automate deployments, I would look to the git repository automation.
Does anything change if you’re in a Direct Lake mode? Thanks!
Yes.
Why I deploy the lakehouse from dev -> prod, the metadata is not included ?
What metadata are you looking to pass along?
@@ChrisWagnerDatagod in this video we are not changing the Lakehouse we are just moving the same data with DEV to prod