SnapLogic isnโt consistent in how data is passed through various snaps. Itโs often necessary to keep some data obtained early in the flow (e.g. from the source) for use later (e.g. when writing to target). However, some snaps, like the XML Parser, requires that only the data to be parsed is passed as input to it while also not supporting binary headers or such mechanisms to forward data from one side of the snap to the other - effectively removing everything except the data it cares about from the stream.
Thereโs an enhancement request for fixing this posted here somewhere, and weโve written about this to our SnapLogic contacts, so hopefully the following work-around wonโt be necessary for very long, but here it is:
Move the โproblemโ snap to a child pipeline and call it via the Pipeline Execute snap, making sure โReuse executions to process documentsโ is not checked (wonโt work if it is). If needed, at the start of the child pipeline, remove any data not to be used with the โproblemโ snap. The Pipeline Execute snap will output the original input data under $original (as the โproblem snapโ should have done).
