Hi Laura,

No, that's exactly what the managed fields is supposed to do, take an existing field and use it as a 3rd unique value to create a key in combination with the participant Id or the participantId/date (or participantId/visitId) combo.

So is adding any additional columns completely out of the question? Another possible option would be to combine the values in those multiple columns into one single column and treat that single column as the primary key, but this wouldn't work if you aren't able to modify the table to include additional columns beyond the original data.

Regards,

Jon