Dynamic input and output path passing from a run template

[nadiyanazeer]

I have a "run command that executes a Python script and stores a path in a template(eg: Response_Path). In a separate workflow , I need to utilise this path dynamically, and since the "Response_Path" changes with each run, I'm looking for a way to pass it as input and save the output in the same location

[Peachyco]

Off the top of my head, I'm thinking that Workflow 1 writes [Response_Path] and any other relevant details to a file (let's say "Response.csv").

Then, Workflow 2 uses Response.csv as input.

[nadiyanazeer]

Thanks, @Peachyco , for your reply. I have a question regarding Workflow 2. In this workflow, my objective is to transform JSON/XML files into CSV data. If the [Response_Path] represents the path to the JSON/XML files, how can I utilize the [Response_Path] in Response.csv?

[Peachyco · Accepted solution]

@nadiyanazeer 

Once you have [Response_Path], you can pass it to a Dynamic Input Tool, which will use it to find and load your JSON/XML files.

You can configure the Dynamic Input Tool like this so it knows what to do with [Response_Path]:

•  

[nadiyanazeer]

Thanks @Peachyco. I'll be sure to incorporate these suggestions into my work.