Update STATE of the pipeline
Hi all,
We’re planning to leverage publicly exposed Monitoring API to replay the failed messages (based on the State of the pipeline). The challenge we’re facing is, we’re not able to figure out ho...
Forum Discussion
In general, XML data should comply with some defined schema/dtd.
If you’re going “weird” XML to “cleaner” XML, then you should be able to use the XML Parser, with a Mapper, and then a XML Formatter. Or, you could maybe just use a XSLT to transform the XML in just one step, or at least clean it up before processing it further.
Hi @jacob.ramsey,
In general, you should avoid loops with SnapLogic, as it’s not a programming language and the behavior could be unexpected in such cases.
Anyhow, if you can replace the “Select Initial O…” with some data put in a json generator snap and attach the pipeline (.slp file), would be much easier for the community to give you a good answer.
Hi Jacob,
Good day, I agree with Sir Igor avoid loops within you pipeline flow
Usually when I encounter this kind of scenario I will put the streaming documents in an array (before using Group snap) now there’s an easy way by using Gate snap once all streaming documents have been contained in an array you can do you loop by invoking .map() , then at the end of your transformation/validation/etc. use a JSON splitter to stream each item in the array 🙂
