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

Report definition generates an error due to timestamp column



A product file is exported from a DB2 environment into an Oracle environment. An error occurs when running the PegaCRM-Entity-RelationshipGroup-Household.GetHouseholdListByContact report definition in the Oracle environment. 

Error Messages

** ** Name: Property Type: DATETIME, Column Type: DATE, Value: Property Type: DATETIME, Column Type: TIMESTAMP - are not of the same exposed type.

Steps to Reproduce

1. Export the product file from a DB2 system and import the file in Oracle environment.
2. Open the report definition PegaCRM-Entity-RelationshipGroup-Household.GetHouseholdListByContact and run the report.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. A sub-report configured with a comparison between MAX(DateTime) and DateTime fails due to a column type mismatch error. 


This issue is resolved by HFix-23086. The code has been updated to set the column type correctly for DateTime properties with MAX/MIN aggregate applied.

Published July 23, 2015 - Updated October 8, 2020

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