The tab delimited idea sounds good, maybe I’ll use it next time.
NN,
I don’t use the flatfile schema because I’ve had too many nightmares with it. I’ll use it if a client demands it.
I make my csv files the old fashion way, which is string concatenation and is the method that webMethods used in their older EDI adapter model.
What I do, is I make a document that contains all the field value holders for each row in the csv document. Each field is a column value and all the values when concatenated make up your csv record row.
I make a separate flow that generates a csvLine. I usually call it genCSVLine. The signature input is the document and the output is the string. I also wrap my values in quotes, although the tab delimited idea would negate the need for this. Then, I concatenate each output csv line to make up the file. First item is concatenated to second, result is concatenated to third, and so on until all are consumed into one line. Make sure that your delimiter is concatenated as well.
One other way you would do this is to make a flow with a signature input of all fields. Then, append each field value into a new string array and then pass the string list into pub.string:makeString with the separator as a comma. This will also return a string representation of all of the column values.
Many ways to do this.
Ray
#webMethods#Flow-and-Java-services#Integration-Server-and-ESB