Forum Discussion
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
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')}
6 Replies
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
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')}
Thanks deborshi_nag
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.
