Our organization has decided that they only want a single pipeline for each integration we develop (no execute pipeline to pass parameters to another pipeline). They say that this is due to the way their error handling works and that they only want one pipeline referenced when they have an error.
I explain the above because people will probably suggest assigning the variable in a parent pipeline and passing it as a parameter to a child.
I need to pass variables assigned earlier in a pipeline to snaps that occur later in the same pipeline. For instance, I assign a filename variable like:
โtest_โ+Date.now().toLocaleDateTimeString({โformatโ:โyyyyMMddโ})+โ.csvโ
I use it in a File reader snap at the beginning of the pipeline and need to use it again multiple times near the end of the pipeline. At the end of the pipeline I move the file to an archive location and need the file name to do that.
I canโt set parameters dynamically in โEdit Pipelineโ or within the pipeline, and it is difficult to pass a variable from one end of the pipeline to the other. In searching this forum I find that others have this same issue but I didnโt see any solutions other than using parent/child pipelines. Is there an easy way to set a variable early in a pipeline and use it in other snaps that come later in the same pipeline? Other workaroundsโฆ?
Thanks!
