SAVE AS pipeline into different workspace

[amaaiia]

Hi,

I'm trying to SAVE AS my pipeline into another workspace and I'me getting this error:

{"message":"Request failed with 404(Not Found): {\"error\":{\"code\":\"PowerBIEntityNotFound\",\"pbi.error\":{\"code\":\"PowerBIEntityNotFound\",\"parameters\":{},\"details\":[],\"exceptionCulprit\":1}}}, \nrequestid: XXXXXXXXXXXXXXXXX"}

I've tried to SAVE AS some other pipelines just to check if it's an issue of the main one, but same behaviour. I've also tried to SAVE AS into other workspaces, just to check if it's also target workspace issue, but again same behaviour with all workspaces. I can only SAVE AS the pipeline into the same workspace.

By the way, all workspaces are in the same capacity.

I guess it should be possible to SAVE AS a pipeline into a differente workspace..

[Anonymous]

Hi @amaaiia ,

Thanks for using Fabric Community and reporting this issue.
When I tried to repro this issue at my end, I didnot face any issue able to Save as Pipeline in different workspace.

Can you please clear your cache and re-try it again? 
If the error still persists, please let me know that steps you are performing? 
Providing further details will help me to investigate your issue? like what all activities are present in your pipeline, etc.

[amaaiia]

Hi @Anonymous ,

I've reproduced a simple use case. My pipeline in source workspace is very simple, as follows:

That is, in the same source workspace where the pipeline is, I have config data warehouse and I get some data from a table in the warehouse.

In the target workspace I have also a config data warehouse, with the same table created:

However, when I try to SAVE AS, I get the mentioned error.

[Anonymous]

Hi @amaaiia ,

Apologies for the issue you have been facing.
This might require a deeper investigation from our engineering team about your workspace, and the logic behind it to properly understand what might be happening.
Please go ahead and raise a support ticket to reach our support team: https://support.fabric.microsoft.com/support
Please provide the ticket number here as we can keep an eye on it.
Thank you.

[Anonymous]

Hi @amaaiia ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to open a support ticket.
After creating support ticket please provide the ticket number here as we can keep an eye on it.

Thanks

[amaaiia · Accepted solution]

For now, you can't copy a data pipeline into another workspace with SAVE AS if you have references to components in the workspace. As I reference lakehouses from the same workspace, I can't copy them.

Two way to copy a data pipeline from one workspace into another:

- Through deployment pipelines

- Through git code, copying from de workspace A to the workspace B by hand.

Then, fabric will alert of the connections that are deprecated because they are referencing another workspace, and we have to change them one by one.

[Anonymous]

Hi @amaaiia ,

It was great to know that you were able to get to a resolution and shared the answer with the community. We expect you to keep using this forum and also motivate others to do that same . You can always help other community members by answering to their queries