Forum Discussion
Differences in datasets after a deployment pipeline
Hello all,
i have 3 workspaces: dev , staging , production .for this im using deployment pipeline.
i have a report where i have embeded paginated report in it . this paginated report should read from dev db, staging db and production db depending on the workspace.
my question is as follow :
now i know that using deployment pipeline , you can change the server, db name of a paginated report .
but what about embded paginated report ???
is it possible to dynamically change from the emebded paginated report is reading using deployment pipeline .
if not, ? is there a way to implement such a thing ?
thanks for the help
Hi Dani29195 ,
Embedded paged reports do have the ability to dynamically change their data sources as they move through different stages in the deployment pipeline. You can read this topic for some help: Paginated Report and Deployment Pipeline dataset s... - Microsoft Fabric Community
There was also mention of a feature called "auto-binding" that may help make the connections between datasets and paged reports work seamlessly within the pipeline, which would allow for automatic re-binding across phases. I think you can read this document: The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Dani291952 years agoFrequent Visitor
Anonymous thank you for the help.
i will check it and get back to you .
and for the first part , about the differences, any thoughts of what could be the reason ?
thanks Anonymous