Hi,
Actually, A flat file is coming from the customer to webMethods. I am creating the flat file schema.The content of the files has a Header line, detail section with Multiple records and a footer.The thing is the fields in the header are comma separated and the records in the detail level are fixed length and eventually the footer fields are again comma separated.The records inside the detail starts with and I am providing the same exact value in the record definition to match when I am creating the schema to validate.But when I ran the schema from the developer providing the data in the format i mentioned above, even though i am providing the detail level to match in the file as I am providing that value in the record definition it is taking from the header and mapping those header values in the detail section when i am generating the IS document from the flat-file schema which is causing an issue.
it is as follows:
this input file is coming with
Header–> Comma separated
detail → fixed length
Footer–> Comma separated.
I am just wondering,is it a valid way to send the file with two different formats as in this case Comma separated and fixed length. and it looks like the customer prefers that format.
I am under the impression that having one flat file schema and defining the record definition as it is to match the detail level in the file will take care of it reading the file from the detail level ignoring the header. Or Do I need to have 3 schemas ( one for header, one for detail, one for footer) and take care of them separately. Or Do I need to remove the header/footer from the file by using the built in services if they have some in webMetods.Or Do I need to write a java service? Could anyone please advise
Thanks,
Capri_lak
#Integration-Server-and-ESB#webMethods#webmethods-Protocol-and-Transport