Support Article

Presence of ID under keys in class definition

SA-38748

Summary



Both the class PegaSI-Data-InterestRateMaintenance and PegaSI-Int-INTERESTRATES are mapped to INTERESTRATES table.

PegaSI-Data-InterestRateMaintenance does not have ID mentioned under the keys in class definition but PegaSI-Int-INTERESTRATES has it.

This is creating an issue as the external table INTERESTRATES does not have any Id.


Error Messages



1. External data table PRPC1PRIV.INTERESTRATES in database PegaDATA has more than one concrete class mapped to it; these classes include PegaSI-Int-INTERESTRATES and PegaSI-Data-InterestRateMaintenance
2. There is a key mismatch: the keys defined for class PegaSI-Int-INTERESTRATES do not match the primary key columns for external data table PRPC1PRIV.INTERESTRATES in database PegaDATA ; the class keys are [ID] , but the table's primary keys are []


Steps to Reproduce



Open the class instances PegaSI-Data-InterestRateMaintenance and PegaSI-Int-INTERESTRATES and do a test connection from both.


Root Cause



The SmartInvestigate_Payments_DDL_Upgrade_633_0711.sql has an incorrect table name configured and also contained SQL syntax issues.

Resolution



Perform the following local-change steps:

1. To run the SQL provided in the HFix-23170, it will create an ID column.
2. To handle the existing data, follow the below steps given in SA article below *only* for INTERESTRATES table:

https://pdn.pega.com/community/pega-7-upgrade-center/question/sipaymentsjar-failed-import-because-errors-thrown-while

Published May 31, 2017 - Updated June 14, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.