Hi all!
I'm trying to create a custom tab that can update a local table that has a composite primary key - that is, the primary key consists of two different columns.
The Id_Key column in the custom tab is supposed to represent the primary key of the updateable table. But Id_Key is only one column, so I'm not sure how to model a composite primary key. Should I use a second Id_Key column or something?
Probably as easy to set up an id_key column that is an identity(1,1) column with a Unique Index on it for the custom tables and REST API to use and then use the composite key as the primary key.
Notice Tessitura have done this on some of their tables.
Mark