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

Unable to find the exposed property in the report definition

SA-5622

Summary



Developer noticed an issue recently in their Pega 7.1.6 QA environment where out of the box CPM report definition has an issue in finding one of the exposed properties , which has exposed column in the right table with right class mapped during the installation earlier. However the system keeps reporting that it is not an exposed property and it is not able to find that column for the corresponding property in the data schema on that pa_address table. It seems the 7.1.6 system is not able to find the exposed property in the report definition from the data schema with OUTER JOIN scenarios in the report definition areas.


Error Messages



2014-12-24 08:54:20,010 [ http-8443-2] [WorkThread] [ ] [titlementFW:03.01.01] ( rd.resolve.SqlReportResolver) ERROR qa-pega.servicenet.com|192.168.33.25 Windevtest30 - An error occured during resolving the report definition - InvalidReferenceException Address.AddressLine1 Unexposed properties cannot be selected for classes mapped to external tables
com.pega.pegarules.data.internal.rd.reference.InvalidReferenceException: InvalidReferenceException Address.AddressLine1 Unexposed properties cannot be selected for classes mapped to external tables


Steps to Reproduce



1) Create a report definition in 7.1.6
2) with Outer join, referencing exposed property, in a exposed table, in a data schema from other sample database
3) Execute the report definition and see if the system is able to find this exposed property in the run time.


Root Cause



The system was missing several of the CPM specific Data-Admin-DB-Table instances. Specifically for this error, PegaCA-Interface-Address, which maps to the pa_address table, was not on the system. It is through the mapping in this instance that the property in question becomes available.


Resolution



This issue is resolved through the following local change: Add the missing Data-Admin-Db-Table instances.

Published January 31, 2016 - 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