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

Oracle TIMESTAMP issue with Report Definition in Pega Marketing

SA-22238

Summary



A Pega Marketing application contains a copy of RULE-EDIT-VALIDATE VALIDATEFILTERVALUE in PegaMKT-Engine:07-13-01 ruleset.

The implementation of this rule does not handle Oracle TimeStamp correctly. As such, the system fails to save a Report Definition that contains a filter condition of "Current DateTime" is used.


Error Messages



When attempting to Save the Report Definition of LookupFieldMarketingOffers, the screen displays with errors of :

** An invalid comparison value or an invalid column has been entered for the right-hand side of a filter condition: 'E'. Enter a valid column, calculation, or literal value. Filter Value:
** An invalid comparison value or an invalid column has been entered for the right-hand side of a filter condition: 'C'. Enter a valid column, calculation, or literal value. pyFilter:
** .AvailableForFieldEnd[TIMESTAMP(6)], @@pxCurrentDateTime()[DATE] are not of the same exposed type. pyFilter:
** .AvailableForFieldStart[TIMESTAMP(6)], @@pxCurrentDateTime()[DATE] are not of the same exposed type.


Steps to Reproduce



1. Create a Report Definition which reports on a DateTime property exposed as Oracle TIMESTAMP.
2. In filter condition define a SQL function on that property e.g. Current Data Time.


Root Cause



A defect in Pegasystems’ code or rules.

Resolution



Apply HFix-25960.

Published August 23, 2017 - 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