Composite key does not work when using savable list

General
, , ,
1

I’ve created a data type with a system of record and two primary keys (composite key). When I enter records through the records tab of the data type, I’m able to enter new records as long as one of the keys are unique. When I use associated savable page however, the same records are unable to be saved. Saving through the savable page requires that both keys be unique. The composite key is not working when saving records through activities (Call Save)

Why is the behavior different when saving new records through an activity as opposed to through the records tab? How can I remedy this?

I’m trying to prevent duplicate records from being inserted into the SOR.

2

@DevinD16607791 After doing some research, I think the reason for the behavior could be that I had updated the primary key after data type creation.

The following post explains that changing the key in the class does not automatically change the primary key in the DBMS

However, I was still able to add records with a unique composite key on the records tab, but not through an activity… is there any logic behind that?