Conclusion:
The only way to have the "User Destination" activity work
is from a "XML file source" because this activity can make
an invalid xml document with multiple root elements which
seems to be what the "User destination" needs.
How I came to this:
My Pipeline is made of a custom "SQL Source"-activity
that reads out a DataSet.GetXml() XML document
To meet to XSD of the User Destination I use the
XSL Transformation activity to produce the XML
ex.
<Users>
<User>
.. fields..
</User>
<User>
.. fields..
</User>
</Users>
But this doesn't work.
But I got the crazy idea to output this document
to a xml file with the "XML file destination" activity
Then I had to create a second Pipeline that took the
generated file with the "XML file source"-acitivity
and then passed it to the "User Destination" activity.
THIS WORKED!!!
I then discovered that the output of the "XML file source"
activity produced a very different document.
ex.
<Users>
<User>
.. fields ..
</User>
</Users><Users>
</User>
.. fields ..
</User>
</Users>
This document is not a valid XML file since it has multiple
root elements the "Users" element.
And you can't create invalid xml output with the
"XSL Transformation" activity!!!
Is this a BUG or just a naughty way of keeping me busy :)