The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredAsk the Fabric Databases & App Development teams anything! Live on Reddit on August 26th. Learn more.
Hi @Anonymous
So I have begun to create another workspace and wire it up with GIT Source Control.
I want to create a copy of one pipeline from one workspace to another. I'm wanting to keep the same name, but I'm getting an error
message":"Request failed with 400(Bad Request):
Error:
{"message":"Request failed with 400(Bad Request): {\"error\":{\"code\":\"BadRequest\",\"pbi.error\":{\"code\":\"BadRequest\",\"exceptionCulprit\":1}}}, requestid: xxxxxxxxxxxxxxxxxxx"}
I'm getting the same error if instead of saving the pipeline as a new one but try to create a new pipeline with the same name of one in another workspace.
{"message":"Request failed with 409(Conflict): {\"error\":{\"code\":\"PowerBIMetadataArtifactDisplayNameInUseException\",\"pbi.error\":{\"code\":\"PowerBIMetadataArtifactDisplayNameInUseException\",\"details\":[{\"code\":\"PowerBIMetadataArtifactDisplayNameNotAvailableYetException\",\"detail\":{\"type\":1,\"value\":\"The DisplayName is not available yet.\"}}],\"exceptionCulprit\":1}}}, requestid: xxxxxxxxxxxxxxxxxxx"}
Solved! Go to Solution.
Hi @12angrymentiger
Thanks for using Fabric Community and reporting this.
At this time, we are reaching out to the internal team to get some help on this.
We will update you once we hear back from them.
Thanks
Hi @12angrymentiger
Apologies for the delay in response.
The internal team has confirmed that the error comes from the Power BI platform, when an artifact with a same name is recreated right after deleting the existing one. It is known to go away after a few mins.
There is an ongoing fix on this issue. We do not have any ETA regarding the fix.
I will keep you posted regarding the updates.
Appreciate your patience.
Please let me know if you have any further questions.
Hi @12angrymentiger
Apologies for the delay in response.
The internal team has confirmed that the error comes from the Power BI platform, when an artifact with a same name is recreated right after deleting the existing one. It is known to go away after a few mins.
There is an ongoing fix on this issue. We do not have any ETA regarding the fix.
I will keep you posted regarding the updates.
Appreciate your patience.
Please let me know if you have any further questions.
Hello
Is there any workaround to this at all? I have authored a large number of pipelines in our dev workspace and wish to deploy them to our production workspace. I have been getting the 400 error for the last few hours. It worked for one pipeline. I am not deleting anything from the production workspace, just trying to "save as" the package in the other workspace.
Hi @PhantomThread There looks like a workaround for now, which is enabling the GIT synchronization for pipelines (which I believe is in private preview). You have to request this feature to be enabled in your workspace by messaging @makromer
I just private messaged them, so hopefully I can get this feature enabled. Once you get these synced you should be able to do a pull request from one branch to another and refreshed into different workspaces.
Good luck!
I don't have a fix for this either. They said wait a bit but it still has the 400 error. I have to recreate my piplines from scratch in the UAT/PROD workspaces. I wish they could also be synced with source control but for now they are unsupported. That would solve this issue.
Hi, have you solved this somehow? I see pipelines still as Source control not supported. and getting this error when trying to copy it to another workspace. Thanks.
Not exactly. I had to copy it to another workspace as a different name and later go back and rename it. It sometimes works.
Thanks. For me it does not work even I changed the name of pipeline.
Ok. I found out what is the issue. Its. As usual error msg. does not tell you.... but the nested pipeline is a issue. Cause right now u can not call a pipeline from different workspace. So you will get also this message when you try to move pipeline which has pipeline execute activity inside to another workspace.
But I think its an issue. cause right now, there is no other option to move pipeline to another environment workspace. Hope source control will be implemented soon @Anonymous .
Hi @12angrymentiger
Thanks for using Fabric Community and reporting this.
At this time, we are reaching out to the internal team to get some help on this.
We will update you once we hear back from them.
Thanks
User | Count |
---|---|
16 | |
10 | |
8 | |
4 | |
3 |
User | Count |
---|---|
53 | |
20 | |
20 | |
17 | |
12 |