compound key on user business class

mbozenik

I've built a user business class to store historical preferences by year for an employee.   Is there a way to create a compound key on a user business class.  The business class works and has a one to many relationship with the employee business class however I cannot get it to save multiple records.   The key is employee, but I don't see how to add a compound key like employee and year?  I believe in the ontology you can reference a surrogate?  Any help is appreciated.

Legacy Contributor

I'm interested in this answer as well.  I've considered Sets as a way to implement this, but was unable to get "override primary" to work, or to remove ontology symbolic key and use the keyword "primary".  Override primary gives a syntax error because symbolic key is set in the ontolgoy (though the reference guide says this overrides ontology...)  and removing ontology and using "primary" on set results in the lpl save action not doing anything.  Sets would probably still work for me if I could enforce no duplicates and NoKeyChange, but NoKeyChange is noted as not being enforced on sets anymore and "no duplicates" still allows for duplicates on the set, so not sure what that is supposed to do.  I'm fine if my primary key is a UniqueID field if I could have another unique index but that does not seem to work.

So essentially what I want to do is in addition to a unique, no key change index to my business class.  Here is what I tried and seems like it should work according to the guide, but does not:

XYZEEMTrnHdrPOC is a BusinessClass
prefix is cfg

Ontology
symbolic key is XYZEEMTrnHdrPOC

Persistent Fields

Hdr1 is Alpha size 200
default label is untranslatable:"Header 1"
Hdr2 is Alpha size 200
default label is untranslatable:"Header 2"
Hdr3 is Alpha size 200
default label is untranslatable:"Header 3"

Sets

TranslationHeader
override primary
no duplicates
indexed
Sort Order
Hdr1
Hdr2
Hdr3

Field Rules

Hdr1
required

XYZEEMTrnHdrPOC is a KeyField

Representation
type is UniqueID

Ontology
business class is XYZEEMTrnHdrPOC

(sorry the indenting didn't come through on the cut/paste, but its there)

I can probably still get this to work to some degree if I modify the Create and Update actions to check for existing values in the set and enforce uniqueness but this seems prone to allowing bad data to make its way into the business class and not the best design overall.