How will you handle the case where | is in the data?
Another possibility, though a bit ugly, is to define dummy fields in the FF schema that never have data in them. This will cause the FF generation to create empty fields – resulting in || between each “real” field.
Ugly. But perhaps more acceptable than a replace ‘|’ with “||” that could go astray depending upon data content.
I’d be interested in learning more about what that impact might be. Delimiters should be changeable without much fanfare. We’re back to wondering why they did this in the first place.
#flat-file#delimiter#webMethods#Integration-Server-and-ESB