Feedback

Feedback

Did this article resolve your question/issue?

   

Article

DTM segments are not exported as ISO date in the comment after the value

Printable View

Information

 
TitleDTM segments are not exported as ISO date in the comment after the value
URL Namedtm-segments-are-not-exported-as-iso-date-in-the-comment-after-the-value
Article Number000110394
EnvironmentProduct: XML Converters
Version: 6.2
O/S: All Supported
Database: N/A
Application: N/A
Question/Problem Description
DTM segments are not exported as ISO date in the comment after the value, uri parameter 'iso' has no effect 

field DTM0102 does not include a comment after the value date in ISO date format.

<DTM0102><!--2380: Date/time/period-->201901141134</DTM0102>

For X12 this seems to work.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
This behavior is because in X12, there is a "date" datatype, so the converters are able to parse it. 

In EDIFACT, there is no "date" datatype, only ALPHA, NUMERIC, and ALPHANUMERIC types. 
Resolution
If an EDIFACT-derived type of EDI is being used, such as EDIFACT or IATA/PADIS, then starting in patch 6.2.0.1893aj there is a new option svd=yes which will validate many instances of the date in the DTM segment (this is documented in the release notes). 

However, since the date format is specified by a previous value in the row, and the validation is very flexible as to the various formats (92 at last count, including things like "A period of time specified by giving the start semester of a year followed by the end semester of a year (both not including century)"), the formatted date in a comment is not explicitly republished, But it will have to be validated. 

Comments are reserved for types which have a single rendering format. 

Additionally, the reason this is an option and not always engaged is because it is possible for the user to add their own format specifiers, and the XMLConverters do not have a way to parse and validate those. 
Workaround
Notes
Last Modified Date2/20/2019 6:27 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.


Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use Privacy Center Security Center Trademarks License Agreements Code of Conduct Careers Offices
Do Not Sell My Personal Information