I am trying to use convertToString to create an EDI file. The service takes a document T810DT, which is created from EDIFFSchema T810. In the schema, some fields have length constraints. So if I have some bad data in the input T810DT, it won’t create an EDI string. I have two questions:

1. Can we generate an XML schema out of the flat file schema so that the length constraits will be usable? ( then I could convert the T810DT to an XML node and then validate it against the xml schema to catch the bad data)

2. Why is the errorArray always null even something wrong really happens in convertToString?

Thanks!

Hi,

Please take some time and register your self.

Regarding EDI validation procedure,check this thread link.,
[url=“wmusers.com”]wmusers.com

you have to pass the valid EDI 810 segment structure,field data then only convertToString (based on the ffschema) it will internally validate and creates the EDI String.

So make sure in the edi mapping is done correctly,based on the EDI messageguidlines (specification),or use any Specbuilder tool to know about on the EDI Segments/Field length constraints.

HTH,