Support Article
Exception on non exposed join condition
SA-64177
Summary
During a New Customer Service installation, error occurs for a report definition that joins on multiple classes.
AppGetAccountList report is configured on PegaCA-Interface-Account class.
Error Messages
An error occured during resolving the report definition - One of the join conditions involving the following unoptimized property is not allowed, since it can severely degrade performance: link.AccountNumber in class PegaCA-Link-ContactAccount. Revise the join conditions or optimize the property.
Test connection on the class used in the Link condition, PegaCA-Link-ContactAccount displays the below error messages:
1. External data table pegadata.pa_account_link in database PegaDATA has more than one concrete class mapped to it; these classes include PegaApp-Link-ContactAccount and PegaCA-Link-ContactAccount
2. There is a key mismatch: the keys defined for class PegaCA-Link-ContactAccount do not match the primary key columns for external data table pegadata.pa_account_link in database PegaDATA ; the class keys are [AccountNumber, PartyId, PartyType] , but the table's primary keys are [pegadata.accountnumber, pegadata.dateadded, pegadata.partyid, pegadata.partytype]Steps to Reproduce
Not Applicable
Root Cause
Sample schema and data were not installed.
Resolution
As a local-change, install the Customer Service sample schema and data.
Published October 6, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.