Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to modify Oracle Date type to VARCHAR2(8)

SA-79493

Summary



Unable to modify the Oracle Date type to VARCHAR2(8). This occurs when using Oracle as the database and a Pega Date property which is attached to the Oracle Date property.




Error Messages



pxResults(1).pyDateValue(1): 17-JUN-1 is not a valid date value .pxResults(2).pyDateValue(1): 18-MAR-1 is not a valid date value .pxResults(3).pyDateValue(1): 16-SEP-1 is not a valid date value .pxResults(4).pyDateValue(1): 17-JUN-1 is not a valid date value .pxResults(5).pyDateValue(1): 18-MAR-1 is not a valid date value .pxResults(6).pyDateValue(1): 18-MAR-1 is not a valid date value .pxResults(7).pyDateValue(1): 18-MAR-1 is not a valid date value .pxResults(8).pyDateValue(1): 18-MAR-1 is not a valid date value


Steps to Reproduce



Drag and drop the Pega Date property to the Report browser while editing a report.


Root Cause



This issue was determined to be a product enhancement request.


Resolution



An enhancement request, FDBK-60318 is created for consideration by Pega Product Management.

Published August 15, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us