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

Issue in Optimizing Properties of type DateTime

SA-33176

Summary



The user is exposing the column for optimization using the SQL script, as a result, on PEGA side it is getting mapped to incorrect type. If property optimization is done using the designer studio then it works fine.

Error Messages



Not Applicable

Steps to Reproduce

  1. Create property of Type DateTime.
  2. Run the SQL script to add column to the respective table.
  3. Check the class instance and DB mapping.


Root Cause



A defect or configuration issue in the operating environment:

In the user's environment column was getting added as of type TIMESTAMP(7). Timestamp support was added after 7.1.8 release. Column type needs to be changed to DATE.

Resolution


  1. Perform the following local-change:

    Modifiy the SQL script and change the column type to DATE.

  2. Retested the class connectivity, also verified if the correct mapping is shown on the PEGA side.
Suggest Edit

Published February 4, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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