Forum Discussion

rriley99's avatar
rriley99
New Contributor III
3 years ago
Solved

Referencing an earlier Snap

Hello. I'm trying to pass a JSON as a pipeline parameter, and I've prefixed my pipeline with a Mapper Snap to "parse" the JSON and the output of the Mapper is a JSON object I can reference later in ...
  • rriley99's avatar
    rriley99
    3 years ago

    Ah, I don't know how I missed this. So I was able to do something like "JSON.parse(_input_params).foo.bar.bin". It's the same step as was in the mapper. 
    I'm not sure if this is more efficient than having a "set variable" function, but since that's not possible I think this will suffice.

alchemiz's avatar
alchemiz
Contributor III
3 years ago

Hi rriley99 ,

Good day, try passing the JSON parameter in Base64.encoded format then decode the string during parsing .. 

As a suggestion you can use the expression library where you can put all this properties and yes you can access this properties anywhere in the pipeline by using the lib namespace e.g lib.inputParams.extract.target.target_bucket

https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438110/Expression+Libraries

Encoded Base64 json
ew0KICAgICJleHRyYWN0Ijogew0KICAgICAgICAic291cmNlIjogew0KICAgICAgICAgICAgInNjaGVtYSI6ICJwdWJsaWMiLA0KICAgICAgICAgICAgInRhYmxlIjogInRhYmxlIiwNCiAgICAgICAgICAgICJhY2NvdW50IjogIi4uLy4uL3NoYXJlZC9zb3VyY2UtZGV2IiwNCiAgICAgICAgICAgICJwaXBlbGluZV9uYW1lIjogInByb2plY3RzL3NoYXJlZC9xdWVyeV9leHRyYWN0IiwNCiAgICAgICAgICAgICJsb2FkX3R5cGUiOiB7DQogICAgICAgICAgICAgICAgImZ1bGwtbG9hZCI6IHt9DQogICAgICAgICAgICB9DQogICAgICAgIH0sDQogICAgICAgICJ0YXJnZXQiOiB7DQogICAgICAgICAgICAiczNfYWNjb3VudCI6ICIsLi4vLi4vc2hhcmVkL3MzIiwNCiAgICAgICAgICAgICJ0YXJnZXRfYnVja2V0IjogImRldi1idWNrZXQiLA0KICAgICAgICAgICAgInRhcmdldF9wYXRoIjogInNuYXBsb2dpY190ZXN0LmNzdiINCiAgICAgICAgfQ0KICAgIH0NCn0

Thanks,
EmEm

rriley99's avatar
rriley99
New Contributor III
3 years ago

Every pipeline (not execution) would have a different set of parameters, so I don't think using an Expression Library would be optimal (not static enough). It wouldn't be a deal breaker, but I would REALLY want these to be human-readable for debugging and monitoring purposes.