Currently, in the database view, I can add my name as a participant more than once if I decide to buy an additional ticket after I purchase the first one. In RENXT, it does not allow me to do the same thing, When I go the web view and open the same event, it does not allow me to add my name more than once. Wehn we want people to use the web view, this causes us concern.
Here are some more use cases ...
1) I have quarterly class events where a single person could be a teacher, teaching assistant, student or applicant. Each participant could have one or many Event Options/custom fields. Our internal business rule is that a constituent/participation type must be unique but RE/NXT isn't letting me add someone more than once.
2) I have an annual event where a single person is unique based on constituent/registration date. Again, each participant could have one or many Event Options/custom fields. Our internal business rule is that a constituent/registration date must be unique but RE/NXT isn't letting me add someone more than once.
In both situations, we use the number of participant records to determine level of engagement and build decision logic based on the answers we get. In both situations, loading everything into a single participant record per constituent adds complexity not just related to the Event Options/custom fields, but also determining engagement levels.