Forum Discussion
@swright your input JSON doesn’t look correct. If you want to reference two variables, they need to be within the same JSON object. For instance, this is an example of an input document to the REST PATCH Snap that would allow referencing $serviceUrl
and $requestBody
in the Snap settings:
[
{
"requestBody": {
"ExternalIdentifierNumber": "002500012"
},
"serviceUrl": "https://"
}
]
If you wanted two PATCH requests to be sent (sequentially, to different URLs etc), the input body would look like:
[{
"requestBody": {
"ExternalIdentifierNumber": "002500012"
},
"serviceUrl": "https://someurl.com"
},
{
"requestBody": {
"ExternalIdentifierNumber": "ABCD"
},
"serviceUrl": "https://anotherurl.com"
}]
Hi Robin,
I’m having some trouble getting it into that format. I’m using a union and somehow that is the output of the union. The target path of mapper2 is the $requestBody.ExternalIdentifierNumber and mapper3 is the $serviceUrl.:
Thanks,
Scott
- pradeepkumar3 years agoNew Contributor II
Can you tell what are you using to route in Binary router snap Please
- svedantam3 years agoNew Contributor
Hi @pradeepkumar,
- pradeepkumar3 years agoNew Contributor II
Hi @svedantam
I hope these works you just need to add one more output view to the binary router in your pipeline and use for error and also toggle first match and see the output.
- darshthakkar3 years agoValued Contributor
Hi @svedantam,
As per the error message, you need to have a snap before “Binary Router” snap as it is looking for a source data, if I may ask, did this pipeline run before you attempted to create an ultra task?
Source systems could be anything ranging from a flat file, snowflake, oracle, salesforce, etc.
Thank you.Regards,
Darsh