Differences in datasets after a deployment pipeline

[Dani29195]

Hello, 

i m facing a strange behavior while using deployment pipeline. 

when i deploy from dev to test,  power bi service still catch differences between the 2 env  , which shouldnt be happening since i create the dev workspace, while the test workspace was empty, and then deployed from dev to test. 

1.checking the difference, it is showing that i have difference in datatype for some columns. ( specifically 3 columns ) /.

2.for another dataset,  i have 5 differences, 2 of them related to dataytype, and the other 3 related to this : 

how could this be possible ? 

best regards,

thanks for any help .

[Dani29195]

Hello @v-yilong-msft 

it seems that the auto-binding doest not work for embeded paginated reports . 

so i dont think this will work. 

what i need is , that the embded paginated report in the power bi report to change its connection when deploying from staging to production . 

so in staging the embded paginated report should be linked to the paginated report pubished to the staging workspace, 

then when i deploy the report from staging to production, the embeded paginated report should change the link and connect tot eh paginated report published to the production workspace. 

is something like this possible .?  or could be that there are some alternatives for this 

[Dani29195]

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

[v-yilong-msft]

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.

[Dani29195]

@v-yilong-msft 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 @v-yilong-msft