Forum Discussion
Deployment Pipline, staging
Ok. I will check out the pipeline extension you referred to. I have now "solved" the issue by creating alternate workspaces with their own pipeline which I now use for staging and swapping when deployting into production.
Community ChampionMy understanding is the data will not be overwritten unless you changed the model, and the model of the production data doesn't match up with the new metadata from Test.
The assumption is (right or wrong) by the time you get to Production, the model is pretty stable.
Can you give more specifics on the changes you are making?
Ok thanks, so what I am looking for is a way to deploy from test to production (by using the Deployment Pipeline) with changes to the model where the target dataset is not overwritten until the very moment that the refresh is finished. So that the report stays accessible/functionable for the users all the time. Like the way it works (I assume) when I deploy from Power BI Desktop to Power BI Service. Having a downtime for one hour for every such deploy is not really acceptable for our customers.
Is it perhaps possible to achieve this some other way, e.g. by using the XMLA enpoints?
It could be useful to be able to schedule the deployment to nighttime in some way.
E