XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Brian FohlSubject: EDI to XML - any way to relax strict validation of version?
Author: Brian Fohl
Date: 03 Oct 2006 11:04 AM
Hello,

We receive EDI which is sometimes outside of the X12 standards - meaning wrong. Many times "4010 " will be sent in the ISA12 instead of the correct "00401" value. Is there any way to allow the Java conversion API to handle this? We don't want to disable validation completely by using "val=no" because then we would lose nested loops.

Thank you,
Brian

Postnext
Tony LavinioSubject: EDI to XML - any way to relax strict validation of version?
Author: Tony Lavinio
Date: 03 Oct 2006 11:08 AM
The problem is that we need the version identification to be
accurate in order to switch to the appropriate dictionary version.

However, perhaps there could be a relaxing.

What if, when we see the version isn't in the proper format, we
applied the following rules:

1. Ensure there are exactly two leading zeros
2. Trim the results to five digits

Would this solve your problem?

Before we consider doing this, are there other cases of sloppiness
you see in the incoming files? You can communicate directly, and
even send some sample files, by sending email to stylus-field-report
(at) progress.com.

Postnext
Brian FohlSubject: EDI to XML - any way to relax strict validation of version?
Author: Brian Fohl
Date: 03 Oct 2006 11:15 AM
The specific situation that I am seeing a lot of is "4010 " (4010 followed by a space) in the ISA12 element. If you could make changes to the converter to allow for that, and possibly other variations in the ISA12 (variations that could still be narrowed down to the specific version) that would be great. Or offer some way to allow that customization in the adapter URL. We receive a lot of nonstandard EDI, so allowing for variations would be a must for us.

Thanks,
Brian

Posttop
Tony LavinioSubject: EDI to XML - any way to relax strict validation of version?
Author: Tony Lavinio
Date: 06 Oct 2006 09:17 AM
This specific change will be in an upcoming version of Stylus Studio.

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.