Feedback
Did this article resolve your question/issue?

   

Article

How to specify different segment orders with XML Converters.

Information

 
TitleHow to specify different segment orders with XML Converters.
URL Namehow-to-specify-different-segment-orders-with-xml-converters
Article Number000118165
EnvironmentProduct: Connect for XML Converters
Version: 6.2
O/S: All Supported
Database: N/A
Application: N/A
Question/Problem Description
How to specify different segment orders with XML Converters.  Sometimes it is useful to be able to rearrange segment orders for an XML Conversion.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Use the pipe symbol to allow the segments to be in any order.

Instead of doing the following in the SEF file: 
...[FAR,C,9][ SSR ,C,99][ ADD ,C,999]... 

The following can be done:
...[FAR,C,9][ SSR|ADD ,C,999]... 

Using the pipe symbol means that the segments SSR and ADD can appear mixed together in that location, in any order, up to the count. 

This can be done with more than 2 segments, and can appear multiple times in the SEF file as needed. 

Also, when using Stylus Studio, while there is no way in Stylus Studio to insert this syntax, if the file is changed manually, it will show up as a #Choice node in the tree view and will be preserved. 
Workaround
Notes
Last Modified Date11/12/2018 5:41 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.