Last activity: 7 May 2019 2:08 EDT
No error thrown at commit for primary key violation
Observing a strange behavior. Created a data type in Pega that has couple of columns and two columns as a combination for primary key. (UserID and DateTime)
When a record is saved to this table through an activity using Obj-Save and Commit having null values for both these primary keys- the activity is executed successfully and no error occurs during run time- Tracer is Clean. The same is observed when a duplicate record is saved (having same pzInsKey). Although this record is not added to the table, as expected.
What can be the reason for this behavior. Could this be due to creating the data type in an improper manner. I already deleted it once and recreated a new one. Still facing the same issue.