Forum Discussion
Auto Binding Feature Not Working with Deployment Pipelines
Hi, I need some help troubleshooting and fixing what appears to be an issue with Auto Binding and Deployment Pipelines not playing nice.
As of a few days, it appears that when deploying a dataset from Test workspace to Prod workspace, the underlying dataflows which also have the same workspace structure do not switch to the Prod workspace dataflows. The deployment rule correctly changes the DW connection from Test to Prod, but not the Dataflows being used.
This only happens in the Dataset deployment pipeline and only from Test to Prod workspaces.
Is this a bug on the Microsoft side wrt Auto Binding? AFAIK nothing has been changed to the deployment pipelines, deployment rules etc. I have gone so far as to delete all deployment pipelines and recreate them with the same deployment rules, still not working.
Hey rubayatyasmin, thanks so much for the suggestions!
Since posting this I rebuilt all the deployment pipelines and reimplemented the deployment rules. It initially didn't work, but today, somehow, everything is working as expected again.
I'm wondering if rebuilding the deployment pipelines worked, it just took some time to create the binding between the workspaces and stages of the deployment pipeline.
3 Replies
Hi, Anonymous
To troubleshoot your issue, follow these steps:
Check Workspace Configuration: Verify that all workspaces are in the Power BI Service (not in Power BI Desktop) and they have been created using the "new workspace experience". Also ensure that you have proper permissions in all workspaces.
Examine Deployment Rules: Validate all deployment rules to ensure that they are correct. As you have mentioned, they should change the data source connection from Test to Prod.
Validate Dataflow Connection: Check your dataset's connection to the dataflow. Sometimes, if the dataset is not correctly connected to the dataflow, it might still be pointing to the old one even after deployment.
Check Dataset Configuration: Make sure your datasets are using parameters for dataflow and other sources. This allows the pipeline to change the sources when deploying between stages.
Manually Update: If all else fails, manually updating the dataflow references in the deployed dataset can be a workaround, though it shouldn't be necessary.
This should help identify any issues with the deployment process.
Hey rubayatyasmin, thanks so much for the suggestions!
Since posting this I rebuilt all the deployment pipelines and reimplemented the deployment rules. It initially didn't work, but today, somehow, everything is working as expected again.
I'm wondering if rebuilding the deployment pipelines worked, it just took some time to create the binding between the workspaces and stages of the deployment pipeline.
good to know that it worked. sometimes it takes time to process all the changes.
