PEGA class not saving after DB table keys are changed
Hi we have changed the key in the DB table from one to two and removed the records and updated the class with two keys but now pega is giving me error while saving the connection.
can some one please guide me.
There is a key mismatch: the keys defined for class A-B-C-D do not match the primary key columns for external data table DB0DPAM0.ONEPA_CLIENT_SKILL_0208 in database CMWSDB; the class keys are [SKILL_ID, SKILL_ID_SEQ], but the table's primary keys are []
here table has two keys.
Pegasystems Inc.
IN
@Sharadk1 Hi Did you save the db table instance after changing the key, if you have already done so please restart your server once and then check
Areteans Technologies
GB
@Sharadk1 While creating tables, pega will create primary key constraints as well and it will map that constraint to the table(database end). It's a tricky affair and the easy way out will be to get rid of the table as you have already flushed the data and let pega create it from scratch.
Lventur
IN
Changing the key value in class instance alone will not be enough to change the key of the existing database table.
- You need to drop the constraint key.
- Then need to run query to update key.
Please refer the below mentioned article, it will show how to get constraint value and to drop the constraint. After constraint dropped how to run query to add new key values.
Coforge
IN
You can follow mentioned approach incase donot have access to DB.
Create a similar datatype again with new primary keys
Open the data table instance of the new data class created and copy the table mentioned there.
Now open the data table instance of your original data class and update the table with the copied table above. Save it & do test connectivity of the data table instance and also for the data class rule where you have updated the keys
Lastly delete the other datatype which you have created (data class, rules created under the class & data table instance)