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

Reports failing on Customer Services Health Care



Exceptions generated when running basic demo scenarios with the Out-of-the-box (OOTB) Customer Services Health Care (CSHC) 7.21 application.
It's a clean and new installation and no customization nor configuration has been made.

Based on the tracer information, the failure is caused by the .Member.pyWorkPartyUri property which is unexposed and yet used in a join condition in the OOTB PegaCPMHC-Data-Claim HCMemberClaimResults Report Definition.

The Claim database table has been checked. Both the MEMBERPARTYURI and the SUBSCRIBERPARTYURI columns are existing.

Error Messages

2016-12-20 11:05:30,435 [   PegaRULES-Batch-2] [  STANDARD] [       MyProject:01.01.01] (  rd.resolve.SqlReportResolver) ERROR   - An error occurred during resolving the report definition - InvalidReferenceException    Address.AddressId    Unexposed properties cannot be selected for classes mapped to external tables

Steps to Reproduce

1) Launch CSHC 7.21.
2) Run basic demo. Exception on screen.


Root Cause

The application has been installed on SQL Server. Pegasystems engine code is assuming SQL Server is case sensitive, regardless of the setting (collation) actually set at the database level. Unfortunately some column names used on external mapping of OOTB classes are having a slightly different name to the associated columns on the database side.


Apply HFix-30970.


Published January 16, 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