What Greg was saying is when you do func=xmlexport all the other params are documented in code and its documentation.
No qn is silly so don't be afraid to ask.xmlexport is designed to move data in small batches.It never had support to create permission sets.what it was doing and you may have mistakenly understood is
Finds the node to be exported
Did user ask for metadata then put category info
Did user ask for permissions info then put permission info.
and on and on like that
If you then bring it to another livelink and try to import it it will fail on all lines
that are inconsistent.If the category dataid is not present,if the user and group is not present
that way.So usually before we migrate data we build all the "building blocks" in the target system.
Common sensically that would be users & groups,Categories,classifications.I have written a poor mans guide to
how to do a small system copy in communities.opentext.com although it may not work in a CS10
scenario
Now if you were exporting that not to be used in another livelink you will be fine.
In CS10 and older there are changes in xmlexport and will not work just like that
because of a new "GUID" field that CS10 expects.If you can fake GUID's
then it may actually work.Sorry I did not test it it was suggested to me by a friend.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010