Hi koryknick ,
Thanks for your reply.
The ID is part of POST body request.
Within parent pipeline, Json splitter is generating its multiple documents which are then passed to child pipeline via pipeline execute.
When next iteration happens and child pipeline is called, I am not able to retain the response from first iteration. how to solve that?
Thanks
You will have to map the content to send in the post using a mapper to the target format expected if it is JSON.
Then you can set the HTTP Entity in the rest post snap to the path of the root of the content/structure you wish to send.
Based on your need and the requirements on the data you will post you can also play around with XML generator or JSON generator to build the target document using velocity templates, sometimes that could be an easier way (visually) if it is a more complex structure you need to map and post.
If you are still facing challenges please post some example on how the json is structured from the previous snap and how your POST request is expected to be sent and structured.
Can anyone suggest, please?
Hi, can anyone suggest me a workaround, please?
Hi @amit.saroha,
The values that are passed from parameters, are always a string. So in your case, you’re not passing a function, but a string.
In order your pipeline to work is, either leave the BatchParameter to get the date directly from the pipeline execute like shown on the picture above, or, use the eval() function with the parameter.
eval(_Effective_Date)
That way your function passed like a parameter, will be evaluated and considered as a function.
Hope this helps,
Bojan
Thanks @bojanvelevski - It works but when I pass 2022-11-20 in same parameter instead of expression the eval (Effective_Date) returns 1991 but I need it as it is 2022-11-20.
Please suggest if there is a way to do it, I want both the options working.
Hi @bojanvelevski, yes, it will be a manual run. I tried the expression you have suggested but it didn’t work. Could you suggest what is wrong what I have done.
