Forum Discussion
Hi @manohar,
If I understand correctly, you don’t need those fields in the final result, if their value is null ?
If that’s the case, you can try the following expression:
sl.ensureArray($attachments.attachment.filter((v,k)=>v!=null))
and map the Target path as $attachments only.
Let me know if this helps,
Bojan
By ‘multiple inputs’, do you mean there are multiple input documents that you want to combine into a single XML document? In other words, the two SQL snaps to the left the XML Formatter are generating multiple output documents and you want to merge those into a single XML doc? If so, you are correct that that is not directly supported in the top-level ultra pipeline. Instead, you’ll need to put those snaps in a child pipeline and use PipelineExecute to do a local execution of the child. So, the child will execute the SQL queries and then generate the XML doc that is the response.
T, thanks for responding!
No, not separate documents input. Just multiple fields.
Here is a screenshot of my input JSON…
… an here is my errored XML Format snap.
“IncidentDescription” is my second field on the input side. ☹️
Ha… I figured it out.
The error said to verify that the document is XML convertible… so I played around with my mapping in the preceding Mapper snap.
I added a common root to call of my fields… “1.”… and that satisfied the XML Formatter snap.
Its always simple once you know what to do. 😉 Regards - David.