@nshruthi
No I didn’t. Unfortunately SnapLogic doesn’t have an out-of-box solution in the XML parser to handle XML array transformation gracefully. I have an enhancement request opened with support but I haven’t heard any resolution on it yet and still waiting…
Hi
I am new to SnapLogic. I need to use the Snap to parse XML file which has multiple elements and nested structure. Do you know where can I start to learn the XML parser or some Snaps? I found really limited resource available on Youtube, Google.
Regards,
Jim
When you trigger a pipeline with a POST, the body is passed into the pipeline as an input document. So you can’t pass pipeline parameters per se, but you can still parameterize the snap fields off of the input document.
You can pass the bearer token in the Authorization header to avoid passing that in the URI as well.
Ohhh. The body is passed as a document. That would explain it. So the only way to pass in parameters is to pass them in the URI?
The only other option is to pass them through headers.
Is there a benefit to using custom headers over URI parameters?
Not from SnapLogic’s point of view. I’d say it’s more of a API design choice. I guess one difference is that the JCC will log the URI (jcc_access.log), so if there were parameters you didn’t want logged out, it’d be better to use a header. Otherwise, I think it’s a matter of taste.
