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

Difficulty creating sub-reports with integer keys

SA-12169

Summary



User is trying to create a sub-report in a Report Definition which matches key columns which happen to be integer database columns. The Pega data type is integer reflecting the database column type of int. When user attempts to configure, user is prevented from doing so because the type at the validation is comparing the Pega type of the column in the master parent report to the database column type.

DB is MS SQL Server 12.



Error Messages



** sub1.person_party_id[INTEGER], .person_party_id[int] are not of the same exposed type.

If you try to use conversion to compare you still ultimately are comparing a Pega Integer with a db int:



Error:
** ** Name: Property Type: INTEGER, Column Type: INT, Value: Property Type: INTEGER, Column Type: INTEGER - are not of the same exposed type.



Filters None



Error:
** ** Name: Property Type: INTEGER, Column Type: INT, Value: Property Type: INTEGER, Column Type: INTEGER - are not of the same exposed type. ** Name: Property Type: INTEGER, Column Type: INT, Value: Property Type: INTEGER, Column Type: INTEGER - are not of the same exposed type.
Displaying 0 records
sys_update_date

No items


Steps to Reproduce



Create a report which has a sub-report with an int database column being the common key for the subreport. This cannot be saved.

Root Cause



The root cause of this problem is a defect in Pegasystems’ code or rules. The code that checks for compatible data types does not include "INT".

Resolution



This issue is resolved in new release Pega 7.1.9.
Suggest Edit

Published February 19, 2016 - 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