Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: Tim MeagherHi,
So is the problem with using the XML Data node that you can't exclude the elements and attributes which appear multiple times & then cause the node to output multiple records?
If so, while you can't exclude them, you can create an additional output pin on the node, and name that output pin with the path to the elements you want to exclude.
Then, the repeating elements which are causing the problem would be output to that new output pin, and you can just ignore that output pin - obviously, it would be better to be able to have a parameter to be able to explicitly exclude certain element paths in the provided XML, which I believe is an existing enhancement request.
As an example if you had an XML format like:
<root>
<A>foo</A>
<B>
<B1>
<BB1>something</BB1>
<BB2>somethingElse</BB2>
</B1>
<B1>
<BB1>somethingNew</BB1>
<BB2>somethingElseNew</BB2>
</B1>
</B>
<C>other</C>
</root>
Then if in the node, you create an additional output (so it has 4 outputs) and call the new output "root.B", Then the B, B1, BB1, BB2 elements would be written to that output, and it would have multiple records since these repeat in the data.
However, the main "Data" output would only have one record containing the elements A and C under root.
Tim