Forum Discussion
Minimizing Production Pipeline Migration
As our PBI environment and developers mature we are transitioning from one workspace to a Dev/Test to Production pipeline environment.
Is there a way to let the URLs get re-assigned to the Production reports?
How about migrating the users assigned to dataset security rolls to push to the production environment?
Just trying to minimize manual work as we deploy these reports to the new workspace.
Thanks for any advice. I did a number of searches in and outside of the fabric community.
Generally when you start using Deployment Pipelines, your existing space becomes Production so no URLs and bookmarks are lost. Then you have a one time opportunity to deploy backwards to Test, and again to Dev. Then you start working in DEV going forward.
If you created a new Production environment, then no, you cannot migrate the URLs. They are tied to the workspace. If you are new to this, you could remove the deployment pipeline and start over using the method above (make it Prod, deploy backwards to create Test and Dev). If that isn't feasable anymore, then your users will need to do a one time migration to new URLs.
Security is another reason. You cannot migrate that, so you would need to add them to the prod workspace (or better yet, don't, but add them to the App in that workspace - best practice) and manually remove them from Dev/Test.
2 Replies
Generally when you start using Deployment Pipelines, your existing space becomes Production so no URLs and bookmarks are lost. Then you have a one time opportunity to deploy backwards to Test, and again to Dev. Then you start working in DEV going forward.
If you created a new Production environment, then no, you cannot migrate the URLs. They are tied to the workspace. If you are new to this, you could remove the deployment pipeline and start over using the method above (make it Prod, deploy backwards to create Test and Dev). If that isn't feasable anymore, then your users will need to do a one time migration to new URLs.
Security is another reason. You cannot migrate that, so you would need to add them to the prod workspace (or better yet, don't, but add them to the App in that workspace - best practice) and manually remove them from Dev/Test.Thanks! This answers my question and will adjust how I request workspaces in the future.
