Question

7
Replies
322
Views
HNB Pega (NIPUNPETER)
Huntington Bancshares Inc

Huntington Bancshares Inc
US
NIPUNPETER Member since 2010 15 posts
Huntington Bancshares Inc
Posted: September 14, 2017
Last activity: February 14, 2018
Posted: 14 Sep 2017 15:19 EDT
Last activity: 14 Feb 2018 14:42 EST
Closed

Expression trend reporting causes SQL error after drilling down in summary view reports

After the report is initially run, the summary view's clipboard page's (pySumViewContentPage) SQL Query is correct without any issue.. However, upon drilling down, the SQL query of pySumViewContentPage, errors out with an invalid operator in the WHERE clause: ( ( TRND1ATRND1 ) OR ( TRND2ATRND2 ) )

The change that happens to pySumViewContentPage on the clipboard is, after the drill down, there are 2 additional index values in pyPreparedValues property of the pySumViewContentPage- .pySLADeadline (this property is defined in trend reporting expressions, twice). The 2 indexes did not appear during the initial run of the summary view report. Due to this error when the "Back" button is clicked on the drilled down report, the initial summary view report's (selection criteria) data is not retained.

Attached is the 2 trend expressions that are defined.

Using PRPC 6.3 SP1

***Edited by Moderator Marissa to update categories***

Reporting
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.