Just as a different take on this, in case you are not sending this to a user but perhaps parsing data between one system to another. For instance sending data from a ordering system to a laser cutter that can only take CSV files. Or if the XML file is not a standard xMII query template output.
I've had to do many many of these. Of course it depends on the structure of the XML file. The concept I use is that I read through each "row" of the xml file then through each "column" Depends on your XML structure. The idea is is to loop through each column of each row, building a string, for that row. Then writing it.
Normally in this case I would use the Xml Loader action, then put in a repeater to loop through rows of the xml file, under the left side of that repeater, I'll put in another repeater to loop through each column. You'll need to create a Local property, of string type as a holder for the string you will be building.. Basically you want to loop for each row in the xml doc, then for each column. I use assignments to build a string with a comma separator, If you nest your repeaters, it will look something like this.
Local.BuildString & u201C,u201D & repFileRow.Output{/Row/[#repFileCol.Output{/Row/ColName}]#}
When the row is finished, I use a write file using the append method until the document is done. Donu2019t forget to remove the leading comma youu2019ll get as a result of the string building repeater you use.
I recommend nested repeaters instead of using fixed column number because just incase your source XML file changes, you don't have to change your BLS transaction. It can make the xpath statements a little long, But if you are careful its not to bad. If you are really good with xpath, you can sometimes avoid repeaters completely. But 95% of the time I use them, unless my transaction has performance issues.
These are just outline steps but should point you in the direction you need. Of course my method may not be the optimal so feel free to try others or your own.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.