Forum Discussion
You should be able to reference the other library through the lib
variable. Is that not working?
For example, if you this as the library helper.expr
:
{
chefify: x => x + ' bork! bork! bork!'
}
You should be able to reference it from another library, like so:
{
msg: () => lib.helper.chefify('Hello, World!')
}
Note that if the references are not in functions, but directly in the top-level expression, you’ll need to ensure the libraries are listed in the right order in the pipeline properties.
I found a better way to achieve what i was look for.
But thanks for highlighting this.@tstack
Welcome @ausman - you are correct that you cannot “save” a value back to pipeline parameters, but there are a some easy ways to do what you are looking to do.
One simple method is to have a main pipeline that reads from the SQS queue then calls a child pipeline to do the work on that file. Then the main pipeline can use the $original object value that returns from the Pipeline Execute snap to get the object that was originally passed into the child pipeline.
Another way (which in my opinion is a little more cumbersome) is to use the Copy snap after the SQS read and a Join snap using the Merge merge type after you have completed the work on the file so you can re-use that original value that was returned from the SQS queue.
I’m sure some other clever folks could give you other ways to solve the same issue, but these are pretty simple to understand and implement.
Hope this helps!
Related Content
- 4 years ago
- 8 years ago