Forum Discussion
Power BI deployment pipelines - reassign workspace
- 6 years ago
Hi Anonymous ,
In your scenario, you may click button "Deploy to production" , the deployment process creates a duplicate workspace in the target stage "Production". This workspace includes all the content existing in the current stage. So it is unnecessary to create another workspace for the Production stage.
For reference:
Get started with deployment pipelines (preview)
Best Regards,
Amy
Community Support Team _ Amy
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- 6 years ago
Another option to consider,
in case Production WS is already used by many users and you don't want to reconfigure it,
is to create a new WS and assign the production WS to the new pipeline, and create dev and test WSs again.
If you wish to keep existing pipeline as well, then unassign the dev+test WSs, which will make the pipeline without content again.
then you can re-assign the Prod WS, and re-create dev and test WSs.
Once you have access to the pipeline you can unassign them from the pipeline. It was there from day 1.
if you don't have access, it means that there's another admin to the WS who assigned them and can help you get access, or unassign it for you. if that person is not in the organizations anymore, there are Power BI Admin APis that can help you solve the problem.
- dbeavon33 years ago
Memorable Member
Nimrod_Shalit Thanks for the reply
>> Once you have access to the pipeline you can ...
This still doesn't make sense. No admin of a workspace should have lesser rights than another admin of a workspace. If an admin has the right to create a pipeline, then an admin should have the right to detach the pipeline. In the college class I'm taking (Power BI C-o-E ), this is relationship is known as the transitive property of PBI workspace administration.
Let me put it another way. If the Power BI software is being used for mission critical purposes, it shouldn't be necessary for one admin to try to contact another admin to fix a given problem. All the admins should have equal rights, and shouldn't be tied to an individual person's account. (As you may know, people can get sick or go on vacation or whatever, and may become unavailable. It is very silly if it is possible for a single admin to tie up a workspace, when they become unavailable.)
>> if that person is not in the organizations anymore, there are Power BI Admin APis that can help you solve the problem.
I'm assuming the API is going to allow an authenticated workspace admin to detach a pipeline? If so, I think this is probably the thing that I was missing. Usually a programming API must be built in a way that makes more sense (more than the U/I). Typically it is necessary to put more thought and effort into the creation of a cohesive API. Also your target audience is probably another developer, who is likely to be a lot more demanding than the unfortunate users of your PBI web portal.