We have done DB partitioning on pystatuswork column in postgre DB . When we are trying to create the case the we are getting the like
Commit error: Batch entry 0 INSERT INTO pegadata.pc_XXX_XXXX_Work and at bottom of the error screen the error is like "ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification Call getNextException to see other errors in the batch."
anybody faces such issue then please share your thoughts on this.
Observation: My class is "Is a class group" and only one primary key defined as pyID. Since we are partitioning with pystatuswork, this column is also a primary key now. so i have mentioned pystatuswork also as primary key and tried but no luck and still getting the same error as above.
When i have deleted all key from the class and trying to create case then case is getting created but a warning message poping up like key needs to be define as without key its not going to save in DB.
Shall I change my class as "belongs to class group" as then we no need to define the key for it? but i cant change the exising class from "Is a class group" to "belongs to a class group" as it will through an error since class instances is existing.
please advise and suggest for the resolution. Many Thanks.
***Edited by Moderator: Pooja Gadige to move from Pega Academy to Product, add product details tag, add platform capability tags***