Forum Discussion
Issues with deploymnet pipeline after creating folders in workspace
Dear all,
We have a pipeline in place that connects three workspaces and it worked fine. Recently I added folders to the workspaces, the structure and items are the same in both workspaces. However, I am now unable to deploy reports through the pipelines, I get this error message:
I tried moving the report in question outof the folder to deploy it but that does not work either.
Can someone help please?
Hi Smokey66
The issue you’re encountering typically arises when binding mismatches occur between the source and target workspaces in a deployment pipeline. This can happen due to structural changes like adding or removing folders. Here's a systematic way to address the issue:
1. Check Binding Status
- Open the Deployment Pipeline tool.
- Go to the affected report and confirm its binding status:
- A bound report will have a checkmark showing it is linked between source and target workspaces.
- Unbound reports can cause deployment issues.2. Remove and Rebind Items
- If items appear unbound:
1. Delete the unbound report in the target workspace.
2. Re-deploy the report from the source workspace to re-establish the binding.3. Folder Structure Considerations
- Folders may not always align in the deployment process. Ensure that:
- Folders and their contents have matching paths in both source and target workspaces.
- Avoid using special characters or overly complex paths.4. Test Deployment Without Folders
- Since you tried moving the report out of the folder:
1. Ensure the report is placed in the root folder of the source workspace.
2. Attempt to deploy it again.5. Sync Changes and Refresh Metadata
- Ensure the pipeline metadata is up-to-date:
1. Refresh the pipeline page in Power BI Service.
2. Check for any lingering changes in the deployment pipeline overview.6. Possible Workarounds
- Recreate the Pipeline:
If the issue persists, create a new deployment pipeline and bind the workspaces afresh.
- Contact Support:
If nothing works, gather technical details (from the error) and contact Power BI support for assistance. The issue may involve backend processes requiring manual intervention.---
Please mark this as solution if these steps resolve the issue or if you need additional help!
Appreciate Kudos 😊.
5 Replies
Thank you FarhanJeelani
Hi, Smokey66
In this case, usually the pipeline is already cluttered with your datasetid, reportid, etc. Failure to deploy successfully. You can re-establish a pipeline and then deploy it. As follows:
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- FarhanJeelani
Super User
Hi Smokey66
The issue you’re encountering typically arises when binding mismatches occur between the source and target workspaces in a deployment pipeline. This can happen due to structural changes like adding or removing folders. Here's a systematic way to address the issue:
1. Check Binding Status
- Open the Deployment Pipeline tool.
- Go to the affected report and confirm its binding status:
- A bound report will have a checkmark showing it is linked between source and target workspaces.
- Unbound reports can cause deployment issues.2. Remove and Rebind Items
- If items appear unbound:
1. Delete the unbound report in the target workspace.
2. Re-deploy the report from the source workspace to re-establish the binding.3. Folder Structure Considerations
- Folders may not always align in the deployment process. Ensure that:
- Folders and their contents have matching paths in both source and target workspaces.
- Avoid using special characters or overly complex paths.4. Test Deployment Without Folders
- Since you tried moving the report out of the folder:
1. Ensure the report is placed in the root folder of the source workspace.
2. Attempt to deploy it again.5. Sync Changes and Refresh Metadata
- Ensure the pipeline metadata is up-to-date:
1. Refresh the pipeline page in Power BI Service.
2. Check for any lingering changes in the deployment pipeline overview.6. Possible Workarounds
- Recreate the Pipeline:
If the issue persists, create a new deployment pipeline and bind the workspaces afresh.
- Contact Support:
If nothing works, gather technical details (from the error) and contact Power BI support for assistance. The issue may involve backend processes requiring manual intervention.---
Please mark this as solution if these steps resolve the issue or if you need additional help!
Appreciate Kudos 😊.
MichaeldiasHelper I
Follow what Farham said.
Very well laid out answer which I will be referring to.Have seen similar issues.
May occur if you've deployed directly to that environment before.
So make sure that the obejcts to deploy, including any possibly new folders they are in, are removed prior to the deploymentThank you all for your suggestions and help! Our issue was that we created a folders in all workspaces in the same structure and also in the target workspace. The correct way is to just create them in the first stage and deloy. Power Bi created the folders in the target then automatically.
I also encounter the same error message. "Deployed items with the same name in the target and source stages are not bound."
Why One Semantic Model Deploys Successfully and Another Doesn’t?
A user was able to successfully deploy a powerbi semantic model from a source folder deployed to a target folder but cannot deploy another semantic model from another source folder. The model is currently sitting in a root folder and he is manually moving the model during deployment just to be organized and start deploying from that folder where he moved the model into prod. Do I need to advise him to republish the semantic model inside the folder ,avoid manual moves during deployment and start deploying from the inside of a test folder again? Or any suggestions you may have.
Please help on the unbound items.
