There are certain situations where limiting constituent notes to one-per-record would be particularly useful. An example being our ‘Relationship Summary’ notes where the prospect managers summarise their relationships to constituents. We would obviously not want multiples of these on a record, especially if you want to use these notes in an automated process as the incorrect note may be used.

It would be good to have these configurable in the code table area or some other configuration screen, where you could set whether each type can be limited to one-per-record. This could either have a check to see if multiples already exist when setting it, and therefore stopping the configuration if multiples do exist, or it could only be configurable at the time of creation, as attributes are. Either would work, although the latter would mean that existing records would need to be amended after such a change.