Subject:Convert EDIFACT to X12 or vice-versa Author:John Khalil Date:27 Dec 2007 02:16 PM
Thank you! That fixed it. I ran through the tutorial without any issues after that. I do have a question on the process: Is the xmlconverter software needed to use this feature of Stylus Studios? I have the xmlconverter installed, which I downloaded from xmlconverters.com, but I am unsure if it is even necessary. I am evaluating the software and would like to know if that would also be a requirement. Thanks!
Subject:Convert EDIFACT to X12 or vice-versa Author:Tony Lavinio Date:27 Dec 2007 04:05 PM Originally Posted: 27 Dec 2007 04:02 PM
Stylus Studio includes a copy of both the XML Converters and the
DataDirect XQuery engine. They can both be used from within the
IDE without additional development licenses or even the separate
downloads from http://www.xmlconverters.com/ or http://www.xquery.com/ .
For external deployment, or for development in other environments
such as embedding in Java or .Net applications, a separate deployment
installable and license are necessary.
Subject:Convert EDIFACT to X12 or vice-versa Author:John Khalil Date:28 Dec 2007 04:16 PM
Thank you. One last question on this. When doing the conversion, I get an error saying that a certain element in the X12 that I am converting is invalid. Now, that is s good thing, it checked to see that the document was using valid codes. However, in certain cases, I will need to override the default allowed codes, and add another. For example, the FOB02 element failed because it had the code "D1". That isnt a valid option according to specs. But, I would like to manually add "D1" into the schema file so that it accepts it as valid.
But adding that element into the schema file had no effect. It still reports the D1 as being invalid. How can I override the default validation to add another code? Thanks.