Using passthru results in some messy json that can complicate things by the time it gets to the end, and it seems that there are some snaps that don’t have the passthru option.
I’m not sure how I can use jsonpath($.“$…PARAMNAME”) for this issue. Can I pass the variable somehow using this?
Thanks.
You define PARAMNAME at the beginning of the pipeline, use passthru where possible, and when you want to use the PARAMNAME later, you use jsonpath to get it.
Other possibility is you get the PARAMNAME value, then use a COPY snap with multiple outputs. Then you use a JOIN snap to bring the value back into the pipeline at other later locations where you need it.
Tstack,
Admittedly I didn’t think about the aspect you just explained. Still, it would be nice to change them at the beginning. I’ll be happy with what I have at the moment. That uses a filereader to read a normal csv file, uses a script to pivot it, and a mapper to potentially change values that are then used to execute a pipeline that runs everything according to those variables, passed as parameters. So everything runs appropriately in the proper environments. It is nice to tell the customer Export the pipeline, import into the new environment, and simply RUN! Of course we give them docs, and a little course so they can provide their own support, but initially it is made to be SIMPLE.
Of course there IS that design flaw in the reltio write snap. It doesn’t allow ANY programability. If we could merely use a pipeline parameter to provide the tenant URL, we would be SET! You guys indicated it would be fixed in the new release. It looks like that is coming out TOMORROW. Does that mean WE can use it in QA? It would be great if we could. We just had our first go live without this, and I want this to work well from the beginning.
If we weren’t going to get access, can you make it so we will?
Steve
The Problem is the people who runs the pipeline needs a restricted environment of not editing the pipelines . But when we do that they can not edit the pipeline properties.
