Hi @patan,
I’ve managed to make it run using the Pipeline Parameter but I had to make small modification in the expression library itself.
Expression Library →
compareandfetchfilter_new.expr (553 Bytes)
Next, in the child pipeline in the mapper snap swap lib.arrayLib.getorgId($) with eval(JSON.parse(_expLib).getorgId($))
Child pipeline →
compare and get result from Expression Library_2023_01_03.slp (210.3 KB)
Let me know if this helps you.
BR,
Aleksandar.
@AleksandarAngelevski Thank you for your feedback. but this solution will not work as I have more than 1000 records to be compared. A ternary operator solution might not fit my scenario.
@patan What you want to say is that the Comparator object will contain more documents than it has right now (2)?
The Comparator object will have more documents to be compared than it has now.
@patan Another approach that I can think of is to introduce separate Comparator Parameter in the child pipeline as following:
And in the child pipeline in the Mapper Snap use the following expression:
lib.arrayLib.getorgId($, JSON.parse(_comparator)).
Parent →
invoke-child-pipe-lib-with-170kb_2023_01_03.slp (7.5 KB)
Child →
compare and get result from Expression Library_2023_01_03.slp (212.7 KB)
Expression Library →
compareandfetchfilter_new.expr (148 Bytes)
And this way you can exclude the Comparator object from the expression library.
Let me know if this approach is applicable in your scenario.
BR,
Aleksandar.
