Forum Discussion
Deployment Pipelines and Shared Datasets
Hi LeboeufHarry ,
what you are trying to do isn't supported yet, as it's a cross-pipelines auto conneciton update between datasets and reports.
how it works today is that a report connected to an external dataset (i.e., not in the same pipeline/ WS), will remain connected to the same dataset after deployment.
You can update it also using the 'rebind' API, but it will not help as well since on the next deployment the connection will be overriden again and will point to same dataset.
My suggestion:
To manage versions and updates for the shared datasets, keep a local copy of a sample report in each stage of the pipeline, just to make sure the changes don't break anything important. the Prod dataset will be the one connected to all stages of the reports in other pipelines.
To manage versions and updates of the relevant report, dev/ UAT will be connected already to the Prod dataset, so it's kind of an advantage in a way.
Hope this makes sense as a workaround.
This is how we do it now.
Pbix are following they way up and are altered to the Acc/Prod Datasets and the put in the release folders.
On the next release they are uploaded/published to the Workspaces and App are republished.
We hoped that these pipelines would be the easier solution, works fine if you have real datasources in your report. But as we followed MS in the thoughts of Shared DataSets .. We are ... beeped... 🙂
Might be a good idea for a future enhancement for deployment pipelines.
With the rules it works fine for real datasources, but not yet for linked datasets. Knowing MS/PBI-Team they will find a solution. Then you realy have a deployment process.
Kr, Harry