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.

Troubleshooting: Activity saves a DateTime value in a Date property (Oracle schema issue)

Suggest edit Updated on September 10, 2021


In the following activity, a property defined as a Date type incorrectly returned a DateTime value to the clipboard instead of a Date value.

This activity references the following:  

    • A property called DueOutDate defined as a Date type..
    • A property called DateReceived defined as a DateTime property.
    • A map value rule called GlobalSLATiming. This map value returns a value using the standard function rule @AddToDate()::

When the activity runs: 

    • DueOutDate is set by the GlobalSLATiming.
    • GlobalSLATiming returns a value from @AddToDate to adjust DateReceived by a pre-determined number of days.

The @AddToDate() function should return a Date value (for example, 04/17/2007), but instead it returns a DateTime value (for example, 04/17/2007 11:04:47).

This issue also arises when reports are run using the DueOutDate as an option. DueOutDate is exposed in the database as a Date type. When a report is run, the following error is displayed:

Customize summary criteria ** There was a problem getting a list: code: 1861 SQLState: 22008 Message: ORA-01861: literal does not match format string

This error occurs because the database returns a column type of TIMESTAMP.


Update the database schema so that every date column has a type of VARCHAR(8), never TIMESTAMP.

All Date properties, regardless of the database software hosting your PegaRULES database, must be of the type VARCHAR(8).


Pega Platform 7.1.1 - 8.3.1 System Architect System/Cloud Ops Administrator System Administration
Did you find this content helpful? YesNo

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us