Forum Discussion
Advocate IIIUsing Invoke Pipeline (preview) in Fabric Data Pipeline
Hello Friends,
At present we are using Invoke Pipeline (Legacy) to invoke "Child Pipeline" (Ex: ErrorHandler Pipeline) inside the Primary Pipeline in our Fabric Layers. As the Invoke Pipeline (Legacy) just need the Pipeline Name to invoke so we need to ensure the Child Pipeline is present in the same Fabric Layer (Bronze, Silver or Gold). And this approach help us in deployment to heigher environment (Ex: PPE) as the Pipeline just work if the target environment has the ErrorHandler pipeline in the Target Environment/Layer.
Issues:
As our ErrorHandler is generic and need in all Layers (Bronze, Silver, Gold) so we need 3 copies of this in 3 layers (Bronze, Silver and Gold) as Invoke Pipeline (Legacy) cant access Pipelines from other layers. The new Invoke Pipeline (Preview) does help here as we can give the Lakehouse connection so it help to maintain just one copy of ErrorHanlder, but it fails post deployment to heigher environment becasue the connection is fixed to the lower environment and cant be parameterized.
Is there a solution for this issue where we can have Just one copy of handleError (may be just in Bronze) layer and use it across all layers?
Thanks,
Prabhat
Hi prabhatnath,
Thank you for reaching out to Microsoft Fabric Community.
Currently, Invoke Pipeline (Legacy) is restricted to invoking pipelines only within the same fabric layer (e.g., Bronze, Silver, or Gold). This means that a pipeline like ErrorHandler must exist separately in each layer.
The new Invoke Pipeline (Preview) supports cross-layer invocation, but the connection is fixed and cannot be parameterized for deployment across different environments.
Currently there is no direct way to maintain a single copy of the ErrorHandler pipeline in one layer (e.g, Bronze) and invoke it across other layers.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
5 Replies
v-achippaCommunity Support
Hi prabhatnath,
Thank you for reaching out to Microsoft Fabric Community.
Currently, Invoke Pipeline (Legacy) is restricted to invoking pipelines only within the same fabric layer (e.g., Bronze, Silver, or Gold). This means that a pipeline like ErrorHandler must exist separately in each layer.
The new Invoke Pipeline (Preview) supports cross-layer invocation, but the connection is fixed and cannot be parameterized for deployment across different environments.
Currently there is no direct way to maintain a single copy of the ErrorHandler pipeline in one layer (e.g, Bronze) and invoke it across other layers.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
- v-achippa
Hi prabhatnath,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.Thanks and regards,
Anjan Kumar Chippa
- v-achippa
Hi @prabhatnath,
We wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.Thanks and regards,
Anjan Kumar Chippa
- YevgenyM
Advocate IV
v-achippa
Is it still the case with "cannot be parameterized for deployment across different environments." ?
I have 30 pipelines in Dev (transform_pipe_1, transform_pipe_2, ..., transform_pipe_30)
Which component should I use to make sure it trigger the correct pipeline per enviroment (Dev,Test,PROD)?
I can use dynamic content for the WorkspaceID, but I don't plan to create a library var for each pipeline.
Thanks
