Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Fabric Data Days Monthly is back. Join us on March 26th for two expert-led sessions on 1) Getting Started with Fabric IQ and 2) Mapping & Spacial Analytics in Fabric. Register now

Reply
Ka13
Helper II
Helper II

Parameters to fabric pipeline

I had a question about passing the parameters to the pipeline.


Can we pass the parameters HireDate, fromdate and todate only in the 2nd pipeline? , or to pass all parameters in the main pipeline which will have Invoke pipeline of 2 pipelines?

1. 1st pipeline will invoke the json which has the schema and table.
   
2. To Invoke the other pipeline after the 1st pipeline, and pass the the above values of schema and table to 2nd pipeline and also to pass the values - HireDate, fromdate and todate in the Copy Activity,

Below queries to add in the Copy Activity 
1 ACCEPTED SOLUTION
deborshi_nag
Resident Rockstar
Resident Rockstar

Hello @Ka13 

 

I suggest you set up pipelines only with the required parameters.

 

Pipeline 1 parameters:

- Schema

- Table

 

Pipeline 2 parameters:

- Schema

- Table

- HireDate

- Fromdate

- ToDate

 

Pipeline 3 (the invokiing pipeline or the parent pipeline):

Insert two Invoke Pipeline activities. 

Pipeline 3 parameters:

- Schema

- Table

- HireDate

- Fromdate

- ToDate

 

In the setting of each Invoke Pipeline activities, pass the pipeline3 parameters like so

Schema    String    @pipeline().parameters.Schema

HireDate  String     @{formatDateTime(pipeline().parameters.HireDate, 'yyyy-MM-dd')}

 

I trust this will be helpful. If you found this guidance useful, you are welcome to acknowledge with a Kudos or by marking it as a Solution.

View solution in original post

6 REPLIES 6
tayloramy
Super User
Super User

Hi @Ka13

 

I agree with @pallavi_r, passing them into the first pipeline, and then having the first pipeline execute the second pipeline is a clean approach. 

 

What could also be done is having a master "orchestration" pipeline that takes all the parameters, and then it runs the 3 pipelines only passing in what those pipelines need as parameters. 

 

 





If you found this helpful, consider giving some Kudos.
If I answered your question or solved your problem, mark this post as the solution!

Proud to be a Super User!





Thanks @tayloramy 

deborshi_nag
Resident Rockstar
Resident Rockstar

Hello @Ka13 

 

I suggest you set up pipelines only with the required parameters.

 

Pipeline 1 parameters:

- Schema

- Table

 

Pipeline 2 parameters:

- Schema

- Table

- HireDate

- Fromdate

- ToDate

 

Pipeline 3 (the invokiing pipeline or the parent pipeline):

Insert two Invoke Pipeline activities. 

Pipeline 3 parameters:

- Schema

- Table

- HireDate

- Fromdate

- ToDate

 

In the setting of each Invoke Pipeline activities, pass the pipeline3 parameters like so

Schema    String    @pipeline().parameters.Schema

HireDate  String     @{formatDateTime(pipeline().parameters.HireDate, 'yyyy-MM-dd')}

 

I trust this will be helpful. If you found this guidance useful, you are welcome to acknowledge with a Kudos or by marking it as a Solution.

Thanks @deborshi_nag 

pallavi_r
Super User
Super User

Hi @Ka13 

I would suggest to keep all the parameter related inputs (HireDate, fromDate, toDate) in Pipeline-1 itself along with schema and table names, pass it to Pipeline-2. Pipeline-2 will just do the copy data or any activity.
This will be cleaner approach with one point for all parameters and keeps the second pipeline more reusable for only copy.

If this post helps, please accept this as a solution. Appreciate your kudos.

Thanks,

pallavi_r

Thanks Pallavi

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

February Fabric Update Carousel

Fabric Monthly Update - February 2026

Check out the February 2026 Fabric update to learn about new features.