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

CPM 7.1.2 version has issues with OOTB Report Definitions

SA-10335

Summary



When out-of-the-box (OOTB) Report definitions are run, errors, stating that the properties that are trying to report on are unexposed, are thrown.


Error Messages



2015-04-30 06:09:01,987 [ http-8443-25] [WorkThread] [ ] [Test:01.01.01] ( rd.resolve.SqlReportResolver) ERROR x.com|127.0.0.1 administrator - An error occured during resolving the report definition - InvalidReferenceException ContactString.Carrier Unexposed properties cannot be selected for classes mapped to external tables
com.pega.pegarules.data.internal.rd.reference.InvalidReferenceException: InvalidReferenceException ContactString.Carrier Unexposed properties cannot be selected for classes mapped to external tables
at com.pega.pegarules.data.internal.rd.reference.StreamPropertyReferenceResolver.isValidClassForReference(StreamPropertyReferenceResolver.java:182)
at com.pega.pegarules.data.internal.rd.reference.StreamPropertyReferenceResolver.resolve(StreamPropertyReferenceResolver.java:104)
at com.pega.pegarules.data.internal.rd.reference.GenericPropertyReferenceResolver.resolve(GenericPropertyReferenceResolver.java:150)
at com.pega.pegarules.data.internal.rd.resolve.AbstractFieldResolver.resolveField(AbstractFieldResolver.java:79)
at com.pega.pegarules.data.internal.rd.resolve.AbstractFieldResolver.resolveFields(AbstractFieldResolver.java:60)
at com.pega.pegarules.data.internal.rd.resolve.AbstractFieldResolver.resolveFields(AbstractFieldResolver.java:53)
at com.pega.pegarules.data.internal.rd.resolve.ListResolver.resolve(ListResolver.java:54)
at com.pega.pegarules.data.internal.rd.resolve.SqlReportResolver.resolve(SqlReportResolver.java:76)
at com.pega.pegarules.data.internal.rd.resolve.SqlReportResolver.resolve(SqlReportResolver.java:36)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.resolve(SqlReportExecutor.java:206)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.executeMainReport(SqlReportExecutor.java:109)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.execute(SqlReportExecutor.java:89)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.execute(SqlReportExecutor.java:56)
at com.pega.pegarules.data.internal.PRDataProviderImpl.executeReport(PRDataProviderImpl.java:1240)
at com.pega.pegarules.session.internal.mgmt.Executable.executeReport(Executable.java:10566)
at com.pegarules.generated.definition.ra_action_cpmgetcontactinfo_21ffd7b6a86d0dc25735ae30cac46955.perform(ra_action_cpmgetcontactinfo_21ffd7b6a86d0dc25735ae30cac46955.java:50)
at com.pega.pegarules.session.internal.mgmt.Executable.doAction(Executable.java:3086)



Steps to Reproduce



1. Log in Pega 7.1.6 with CPM 7.1.2.
2. Run the OOTB Report Definitions.
     For Example:
     PegaCA-Interface-Contact • CPMGetContactInfo ( saved in PegaAppCA:07-12-01 )


Root Cause



Application has been upgraded from PPRC 6.2 SP2 and CPM 6.x version single schema to Pega 7.1.6 with CPM 7.1 R2 split schema. 
It is observed that there are few classes added newly in CPM 7.1 R2, which were not present in CPM 6.
 
For Example:
Class name : PegaCA-Interface-Contact-CommunicationOptions.
This should have been mapped to pa_Communication_Options table if the CPM is newly installed. 

In the upgraded environment, it is noticed that PegaCA-Interface-Contact-CommunicationOptions class is mapped to PA_CONTACT table.


Resolution



Map the classes to corresponding tables. For example:

   Class : PegaCA-Interface-Contact-CommunicationOptions to pa_Communication_Options table
   Class; PegaCA-Interface-AddressType  to PA_ADDRESS_TYPE table

Published October 7, 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