READ-XML method returns an unusual error: JSON string is not a valid ISO-DATE. (20015) while reading empty data into the Date field

Jan 23, 2024
Knowledge

Title

URL Name

READ-XML-method-returns-an-unusual-error-JSON-string-is-not-a-valid-ISO-DATE-20015-while-reading-empty-data-into-the-Date-field

Article Number

000199335

Environment

Product: OpenEdge Version: 12.3 OS: All Supported Operating Systems Other: N/A

Question/Problem Description

READ-XML method returns an unusual error: JSON string is not a valid ISO-DATE. (20015) while reading empty data into the Date field

"testproc.p" file

DEFINE VARIABLE mRequestData AS LONGCHAR NO-UNDO.

DEFINE TEMP-TABLE testreq NO-UNDO XML-NODE-NAME "testreq"
   FIELD fDate AS DATE XML-NODE-NAME "TestDate".
DEFINE DATASET dsReq XML-NODE-TYPE "HIDDEN" FOR testreq.
FIX-CODEPAGE(mRequestData) = "UTF-8".

COPY-LOB FROM FILE "test.xml" TO mRequestData.

DATASET dsReq:READ-XML("LONGCHAR", mRequestData, "EMPTY", ?, NO) NO-ERROR.
IF ERROR-STATUS:ERROR THEN
   UNDO, THROW NEW Progress.Lang.AppError(ERROR-STATUS:GET-MESSAGE(1),
                                          ERROR-STATUS:GET-NUMBER (1)).  
CATCH e AS Progress.Lang.Error :
   MESSAGE "Progress.Lang.Error" SKIP e:getMessageNum(1) SKIP e:getMessage(1) VIEW-AS ALERT-BOX.
   DELETE OBJECT e NO-ERROR.
END CATCH.

"test.xml" file

<?xml version="1.0" encoding="UTF-8"?>
<testreq>
   <TestDate/>
</testreq>

Steps to Reproduce

Clarifying Information

- Such message does not exist in promsgs file.
- The problem appeared in OpenEdge 12.3 only. No such message in 11.7.x and 12.2.x

Error Message

JSON string is not a valid ISO-DATE. (20015)

Defect Number

OCTA-33920

Enhancement Number

Cause

This is expected behavior. It is correct that an error is raised in this scenario, because the XML being read is invalid.

The OpenEdge implementation of XML follows the ISO 8601 standard which disallows blank dates.

An empty date XML element is not a valid XML Schema date value unless it is qualified with the xsi:nil attribute with a 'true' value. This attribute indicates whether the element has to have a value, or can be empty or unknown. A true value indicates that the element can be empty or unknown.

However the error message is misleading, as it applies to both JSON and XML. This was introduced by a bug fix in 12.3 (OCTA-8410).

Resolution

Ensure that XML being read doesn't contain empty strings for dates. This can be done by pre-parsing the XML input to remove the empty string date values, replacing them with the XML representation of null. To correct the XML and make it valid to have an empty date field and therefore stop the error from appearing, modify the XML to ensure that nil is allowed in every element that is blank. For example:

<?xml version="1.0" encoding="UTF-8"?>
<testreq xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">;
   <TestDate xsi:nil="true"/>
   <dateValue xsi:nil="true"></dateValue>
</testreq>

Note that in the above XML, the schema reference xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"" can be added to any node that is a parent of the node where the blank value is expressed with (xsi:nill="true").

Workaround

Programmatic workaround
Use the below code as workaround.

DEFINE VARIABLE mRequestData AS LONGCHAR NO-UNDO.
DEF    VAR      mydate       AS DATE.

DEFINE TEMP-TABLE testreq NO-UNDO XML-NODE-NAME "testreq"
    FIELD fDate AS DATE XML-NODE-NAME "TestDate".
DEFINE DATASET dsReq XML-NODE-TYPE "HIDDEN" FOR testreq.
FIX-CODEPAGE(mRequestData) = "UTF-8".

COPY-LOB FROM FILE "test.xml" TO mRequestData.
DATASET dsReq:WRITE-XMLSCHEMA ("file", "test.xsd", TRUE).
DATASET dsReq:READ-XML("LONGCHAR", mRequestData, "EMPTY", ? /*"test.xsd"*/ , NO).

mydate =  DATE("") .                                        
IF mydate = ? THEN
DO:
    MESSAGE "DATE("") is unknown".  
END.
FOR EACH testreq:
    IF fdate = ? THEN
    DO:
        MESSAGE "fdate is unknown".    
    END.
END.

If READ-XML is supplied with the XML Schema for the dataset ('test.xsd' in the above code), the method will fail with "READ-XML encountered an error while parsing the XML Document" 'invalid date value'". (13064)

Notes

Progress Article(s):
000140598, JsonObject and JsonArray Date Handling
READ-JSON raises error 20015 when importing blank date fields

NOTE:
In the fixed version, both XML and JSON versions of the message have been implemented by the fix for OCTA-33920:

JSON string is not a valid ISO-DATE. (20015)
XML string is not a valid ISO-DATE. (20237)

Keyword Phrase

Last Modified Date

6/6/2024 8:41 AM

READ-XML method returns an unusual error: JSON string is not a valid ISO-DATE. (20015) while reading empty data into the Date field

Files(0)

Was this article helpful?

Was this article helpful?

READ-XML method returns an unusual error: JSON string is not a valid ISO-DATE. (20015) while reading empty data into the Date field

Information

Related Articles