Originally posted by: Laurent(Satisco)
If you have the option of using two schemas, then the attached sample may be what you're looking for.
Note that I used REFORMAT (which is not my favourite function) and Native XML schema (out of laziness, and even if it's not my favourite way of doing XML)
The behavior may be different on real data, at least I had bad experiences with REFORMAT. You may succeed using teh Automapper and let it implement all the mapping at every level.
What does the trick here is the constraint on the outpout schema, which requires the Elt2 element to be at least 1 character (and this is the very reason why you need two schemas since the same constraint does not validate an empty element).
Hope this helps
Laurent
#IBM-Websphere-Transformation-Extender#DataExchange#IBMSterlingTransformationExtender