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

Property with declare expression not exported to excel correctly

SA-572

Summary



You are exporting a report to Excel.  You observe that some of the exported values do not match the equivalent values in the original report.  Your report makes use of a join condition.  You run tracer during the export and you observe that backwards chaining takes place during the export.

Error Messages



None


Steps to Reproduce

  1. Create a Report Definition that uses a join.  
  2. Have some of the values of the report be the target of one or more Rule-Declare-Expressions.  
  3. Export the report.

Root Cause



The root cause of this problem is a defect in the Pega code.  The export functionality does not fully rerun the report from scratch, but uses some of the existing data from the existing report.  In particular, a "Page-Merge" is used to copy over some of the existing data during the export; this function is not used during the original execution of the report.

The Page-Merge causes the inference engine to fire to do some backwards chaining.  Because of the nature of the operation and the context in which it is taking place, the Rule-Declare-Expression returns a value which is not the same (and is incorrect) as the value being presented in the report prior to export.


Resolution



HFix-7015 turns off the backwards chaining before the "Page-Merge", eliminating the problem.

Published June 12, 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