Parsing XML Array to JSON array is inconsistent

When using XML parser snap to parse XML documents we are facing a problem when handling XML array type. This is because XML parser parses XML Array at runtime to either a JSON array if the particular element in the incoming XML message comes as array or as a single JSON object/element if the particular element in the incoming XML message comes as a single element not as an array. This is causing a major problem down the processing pipeline especially when using Mapper or any similar snaps where the parsed JSON data comes either as an array or as element {} and pipeline breaks for error.

The question is how can we force XML parser or combine it with any other technique so that it will parse XML element to JSON always as an array even if it comes as a single XML array element. Attached is an example of a simple pipeline reading an xml file with attached schema xsd. If the XML item element cames as an array then the pipeline will process successfully til the tend but if it comes as a single item then it will definitely fails at Mapper because JSON cannot treat it as an array
ParsingXMLArray_2017_07_24.slp (4.5 KB)
shippingtestingschema.xsd.txt (1.2 KB)
shiporder.xml.txt (673 Bytes)
shiporder_OneItem.xml.txt (527 Bytes)

Specifically for your example pipeline, try adding a new Mapper with the following configuration immediately after your XML Parser:

(note the Pass through selection)

1 Like

Thank you @del . This solution resolved my issue.
So let me put it differently now. Aside from my specific example and assuming that I have just to parse from XML to JSON and write it as-is without using any mapping/transformation to a JSON file to an external system but with the array format always enforced even with one element, Is there a way to do it in the XML parser by let us say for example checking the validate against XSD schema? Or do I have to use a mapper always to clean it and enforce the array on it?

The reason I am asking again because the XML I gave was just a simple example but in my real scenario the XML payload I am working in has more than a 100 elements and multiple nested array structure. so that means I have to use a mapper for each expected array in order to check it and use the [].concat[element] on it ?!


Am also looking for solution for similar kind of issue with multiple elements having array structure, Did you find any solution in xml parser or added multiple mappers?


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…


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.


First you have to use the out-of-box XML parser snap and configuring it should be easy as described in SnapLogic documentation. Then the hard part begins after the incoming XML input parsed into JSON is to navigate through the nested structure and map any array or non-existing elements. The best way to do that is to use a series of Mapper snaps and in each mapper you have to use expression language statements which is a subset of JavaScript. To read more about expression language please check the following link:

For example to cast an parsed XML element in JSON into an array type you would use the following expression: [].concat[ element ]

Please refer also to the beginning of this thread for other examples.

Even I too also facing the same issue. while flattening the multiple structure( both single child and multiple child elements) xml source to individual columns to target tables

Could anyone find any optimal solution for this?

I am using JSON Splitter and mapper snap but unable to find optimal solution and in-consistent for different structure of xml.

Please update here if anyone find solution for this.


Use XML schema validation in XML parser with schema file provided.
In the XSD schema lets have the child elements defined with minOccurs=“0” as explicitly defined .
This will help you solve all the issues at all places.

@SEGMENT”: “1”,
“DEV_ALLOW”: “000”,
“E1ABCDEF_0”: [
@SEGMENT”: “1”,
“RATE_TYPE”: “200*”

<xs:element name=“E1ABCDEF_0” maxOccurs=“unbounded” minOccurs=“0”>
<xs:element type=“xs:string” name=“RATE_TYPE” minOccurs=“0”/>