Ænðr E. Feldstraw
Last week my team learned about a limitation in #XML processing in the #BizMapper application by #OpenText (formerly by #GXS):

If an XMLElement has 2 or more children with the same name, and the source format for that element has its sort order set to unordered, then BizMapper no longer knows which child element to pick.

We wanted the 2nd. BizMapper gave us the 1st.

This is understandable behavior. It's also quite annoying. We reached out to their support and hope for a solution.
May 2, 2019 at 8:35pmMastalab
Show threadÆnðr E. FeldstrawMay 2, 2019
This was found due to a parsing error of order information: we couldn't see what our customer wanted had paid for, and wanted us to ship.

#BusinessIntelligence #EnterpriseCommunication

The problem originates with a #ECommerce platform we use: since April 24 they added a UPC field on the order lines. A wrong one: it's identifying a parent/group product rather than what the customer bought.

We contacted that platform's support and await a solution.
Show threadÆnðr E. FeldstrawMay 2, 2019
Now, in an #XML document it is perfectly reasonable to have multiple child elements with the same name. Parsing them just generates an array.

The parser we use however treats the document serially, and returns the 1st matching field, regardless of others with the same name. That may be because we set the document's sort order to unordered.

Temporary solution: preparse and rename the offending field.

Yay for #XSLT.