Forum Discussion
SAVE AS pipeline into different workspace
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.
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
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.
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