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)
-> + Grouping (2)
-> + Best Practice for Pipeline err... (2)
-> + pdf generation (4)
-> + Problems excuting a Pipeline w... (2)
-> + XML serializer (3)
-> + Supported EDIFACT versions (5)
-> - Anyone know XActimate ESX file... (1)
-> + Stylus Studio with OpenJDK (2)
-> - Encoding error when importing ... (1)
-> - SEO Service in Delhi, India (1)
-> - HP Printer Support (1)
-> + Stylus Studio X16 Professional... (5)
-> + Stylus Studio X16 Enterprise -... (4)
-> - Overly complicated formatting ... (1)
-> + java apparently running, canno... (2)
-> + Stylus on Citrix - unable to v... (6)
-> + XSLT and XPath Questions (New ... (13)
-> + EDIFACT D96A CONTRL XML schema (2)
-> + JDK dropdown box empty and Jav... (2)
-> + Replacing XSD files in Report (4)
-> + Cannot locate WYSIWIG tab on X... (3)
-> + EDI X12 xml schema with segmen... (2)
-> + Error Message (4)
-> + jvm disabled message keeps pop... (2)
-> + XTSE0620: An xsl:param element... (3)
-> + Fail in installing “Apache FOP... (5)
-> - Jenkins: about the path of bui... (1)
-> + problem with Stylus X15 XML RE... (2)
-> + Cannot remove a row into a tab... (6)
-> + prevent the meta data from bei... (3)
-> + Unable to auto detect JRE in X... (2)
-> - Unable to auto detect JRE in X... (1)
-> - where to find information (1)
-> + X16 - XPath 3.0, XQuery 3.0, X... (2)
-> - Test (1)
-> + XSLT debugger shows [symbol u... (3)
-> - How do i use *.conv to process... (1)
-> - How do i use *.conv to process... (1)
-> + Not able to configure JVM in ... (5)
-> + Converting Cobol flat file to ... (2)
-> + Problem with uninstall - Windo... (2)
-> + Function current() is not reco... (6)
-> + API or web version (2)
-> + How to use Saxon for X16 on WI... (9)
-> + Error in SS X14 syntax highlig... (2)
-> + Option not available (2)
-> + XML Diff functionality and sor... (3)
-> + Convert Oagis XML file to TXT (4)
-> + DataDirect xqresultsequence is... (2)
-> - xfile Legacy file format suppo... (1)
-> + TPFDF (3)
-> + Help needed with SLSRPT - EDIF... (2)
-> - keeps crashing after I try and... (1)
-> + Can SS do this? (14)
-> - CargoImp support (1)
-> + No Preview Displayed - File is... (3)
-> - Stylus Studio X16 build 1974l ... (1)
-> + Help! Help!Help! Regading form... (2)
-> + FileNotFoundException generati... (6)
-> + FO External Graphic Producing ... (2)
-> + Use of Java methodes (4)
-> + get generated XQuery output on... (2)
-> - right construct for involving ... (1)
-> + SS JRE Version has "Stylus Stu... (3)
-> + Trying to validate an XSD: co... (3)
-> + Disable "Output" windows (4)
-> + Stylus Studio V16 X64 update d... (2)
-> + Could not load the Java Virtua... (2)
-> + .NET XslCompileTransform strip... (6)
-> + XML Report Preview and Save Ev... (8)
-> + X16 Enterprise 32bit crash on ... (5)
-> - MSXML6.0 SAX Parser, "Index re... (1)
-> + MSXML6.0 DOM Parser stops afte... (4)
-> + How to disable checking for up... (2)
-> + XML Publisher requires duplica... (4)
-> + Modifying Field Name in XML (4)
-> + Java Runtime Environmnet Libra... (2)
-> + Passing Parameters and Multipl... (4)
-> + Total Newbie Question... where... (3)
-> + XML Pipeline (2)
-> + Encoding problem in text previ... (5)
-> + New Installation on windows 20... (4)
-> - Exception while calling Java m... (1)
-> + Jars to be included for callin... (2)
-> + SXXP0003: Error reported by XM... (2)
-> + Validation error (5)
-> + Windows 10, latest Java, new t... (2)
-> + using help crashes stylus stud... (3)
-> + Web Service Call error (5)
-> + javax.xml.xquery.XQException: ... (2)
-> + Trang translator is not availa... (2)
-> + Replacement for flat2xml (2)
-> + CONV CSV Display Problem (3)
-> + StylusValidator.exe Command Li... (3)
-> + Cannot run Java built in valid... (2)
-> + Windows 10??? (3)
-> + Stylus Custom XML Conversion (... (8)
-> + X14 enterprise and saxon 9.4.0... (3)
-> + Open an XML document in the XM... (3)
-> + How to generate mapping report... (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
Steve RSubject: EDI delimeters when generating file, db lookups
Author: Steve R
Date: 03 Apr 2006 08:36 PM
I can successfully convert EDI to XML with the EDI adapter. However, when I attempt to save an XML file back to EDI using the adapter, it doesn't appear that I can set the element and segment delimeters.

For example, the ISA segment of EDI file in looks like this:
ISA*00* *00* *ZZ*3216549870 *01*321654987 *060202*1136*U*00400*000002097*0*P*>
TD1**38

The file out looks like this:
ISA+00+ +00+ +ZZ+3216549870 +01+321654987 +060202+1136+U+0400+000002097+0+P'
TD1++38'

-the element delimeter should be an '*' instead of '+'
-the segment terminator ' should not be generated
-the ISA segment should end with '>'

Also, what is the best method to lookup values from a database to place a lookup value in an element? For example, I have a part ID and I need to lookup and use the supplier's part code instead.

Thanks,
Steve

Postnext
Ivan PedruzziSubject: EDI delimeters when generating file, db lookups
Author: Ivan Pedruzzi
Date: 04 Apr 2006 01:27 AM

I would use XQuery (DataDirect XQuery processor) if I was you.
It let you aggregate EDI with the SQL Server data.

See the video tutorials
http://www.stylusstudio.com/xml_videos.html
XQuery
Integrate Relation and XML

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Postnext
Tony LavinioSubject: EDI delimeters when generating file, db lookups
Author: Tony Lavinio
Date: 04 Apr 2006 08:23 AM
You can use PIs to change the separators.
To do what you want, the start of your XML should look like this:

<?xml version="1.0" encoding="utf-8"?>
<?edi_segment \r?>
<?edi_element *?>
<X12>
<ISA>
...

If instead of a CR you want an LF to be your segment terminator, use
\n for the edi_segment PI. And since you are using a CR or LF as the
terminator, you'll want to change the URL option from &eol=yes to
&eol=no, otherwise you'll get extra linefeeds between each segment.

As to ending the segment with '>', that's the component separator,
and is specified as the value of the X12/ISA/ISA16 element. You
could do it just by changing the ISA16 value like this: ISA16>></ISA16>

Postnext
G MoneySubject: EDI delimeters when generating file, db lookups
Author: G Money
Date: 08 Apr 2006 11:38 PM
I'm not finding this last suggestion to work entirely. I'm using SS Enterprise to generate EDI files from XML files and have a hard time getting the lines to end with only an LF character.

I've got a project whereby I'm passing the EDI files onto a mainframe and MUST end my lines (segments with a ~ and a LF). I've tried changing the parameter in the "adpater:" URL but I still get CRLF's. I tried adding \n and \r to the PI and both cause a "Pipe Broken" error when I run the XSLT transform which saves via EDI using the adapter... So maybe I'm just making some mistake or is it really not working.

The suggestion to use the PI's to change the element delimiter to * and the segment delimiter to ~ worked like a charm and you have no idea how happy I am about that b/c the solution to that evaded me for weeks!!! (I've been working around it by post-processing the files with another program)

Just for reference, I'm generating an X12 844 in this case but the linefeed problem exists for every EDI file I try to generate.

SS rocks and thanks in advance for your help!!! :-)

Postnext
Tony LavinioSubject: EDI delimeters when generating file, db lookups
Author: Tony Lavinio
Date: 10 Apr 2006 09:36 AM
If you need just a linefeed, change the \r in the example I gave
to \n, and you should be set.

Postnext
G MoneySubject: EDI delimeters when generating file, db lookups
Author: G Money
Date: 10 Apr 2006 09:53 AM
<i>If you need just a linefeed, change the \r in the example I gave
to \n, and you should be set.<i>

This is exactly what I did, and it gives me errors. :-( I put the \n in there and got a "Pipe Broken" error.

Postnext
Tony LavinioSubject: EDI delimeters when generating file, db lookups
Author: Tony Lavinio
Date: 10 Apr 2006 01:06 PM
I tried here with release 2, and it worked fine. Can you
post the first few lines of your XML file?

Also, how are you writing this? As output of XSLT or XQuery,
or just doing a File|Save As from the editor for testing?

Here's exactly what I used:
<?xml version="1.0" encoding="utf-8"?>
<?edi_segment \n?>
<?edi_element *?>
<X12>

As a side point, you may want to make sure that the encoding at
the next level knows the encoding of the EDI document; you might
want to set enc=ISO-8859-1 or even US-ASCII if that's what the
mainframe is expecting.

Postnext
G MoneySubject: EDI delimeters when generating file, db lookups
Author: G Money
Date: 10 Apr 2006 07:03 PM
Originally Posted: 10 Apr 2006 07:01 PM
I'm using build 501f at the moment and I see there's a newer version out there so I'l try to pull that down to see if it works. I'll also take a stab at different encodings. BTW, to answer your questions, I'm generating the XML as part of an XSLT transform scenario and the scenario is automatically saving to the EDI file using the EDI adapter. The scenerio is currently using the XalanJ 2.5.2 processor. The first couple of lines from the generated XML are: <?xml version='1.0' ?> <?edi_segment \n?> <?edi_element *?> I also generated: <?xml version='1.0' ?> <?edi_segment ~\n?> <?edi_element *?> Which was equally unsuccessful.... This works and is what I have in there currently but comes out with CRLF's at the end of segments (lines) instead of the desired LF only. <?xml version='1.0' ?> <?edi_segment ~?> <?edi_element *?> Thanks.. I'll write back again after trying to use Release 2 I suppose.

Posttop
G MoneySubject: EDI delimeters when generating file, db lookups
Author: G Money
Date: 10 Apr 2006 07:04 PM
I guess there's a problem with editing posts so I'm reposting hopefully with all of my carriage returns. :-)

I'm using build 501f at the moment and I see there's a newer version out there so I'l try to pull that down to see if it works. I'll also take a stab at different encodings.

BTW, to answer your questions, I'm generating the XML as part of an XSLT transform scenario and the scenario is automatically saving to the EDI file using the EDI adapter. The scenerio is currently using the XalanJ 2.5.2 processor. The first couple of lines from the generated XML are:


<?xml version='1.0' ?>
<?edi_segment \n?>
<?edi_element *?>

I also generated:
<?xml version='1.0' ?>
<?edi_segment ~\n?>
<?edi_element *?>

Which was equally unsuccessful....

This works and is what I have in there currently but comes out with CRLF's at the end of segments (lines) instead of the desired LF only.
<?xml version='1.0' ?>
<?edi_segment ~?>
<?edi_element *?>

Thanks.. I'll write back again after trying to use Release 2 I suppose.

   
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.