How to pass job variable set on "Grid Iterator" to a sub-job called through Run Orchestration?

Matillion ETL
1

I have attached a diagram that will help describe the issue, but in summary, I am trying to build a set of layered jobs that are called through Run Orchestration components. The Run Orchestration calling the sub-jobs is attached to a "Grid Iterator". I want to call the sub-job on each loop of the grid iterator and pass the current value of the grid iterator (set on a job variable) into a job variable in the sub-job. The sub-job should only see a single scalar value. However, I have been unable to set the scalar on the "Run Orchestration" to pass the variable value. The only option that seems to work is to set the Grid Iterator value to a "global environment variable" - ideally, I'm trying to avoid this because we prefer to not have a ton of global environment variables to serve purposes that only exist in individual jobs.

 

How can job variables set by grid iterator be passed to sub-jobs called by Run Orchestration?

 

2

You definitely can pass the values of a grid iterator to attached run Orchestration job. Have you tried passing the variables using ${variable_name} ?

3

@AnudeepK​ yes, that does work. We updated our job and was able to pass the iterator value set to a job variable into a sub-job variable using the "Set Scalar Value" on the "Run Orchestration" component - we used the ${variable_name} as you described. Thanks.