Forum Discussion

prabhatnath's avatar
prabhatnath
Icon for Advocate III rankAdvocate III
1 year ago
Solved

Using 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 (Le...
workspaces
  • v-achippa's avatar
    v-achippa
    1 year ago

    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's avatar
v-achippa
Icon for Community Support rankCommunity Support
1 year ago

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

YevgenyM's avatar
YevgenyM
Icon for Advocate IV rankAdvocate IV
1 year ago

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