Hi Samantha!

We are trying to keep a group of constituents together who are associated with the nomination process at any time, (year over year). Those "involved" may be both a nominator and nominee in the same year, or they may be active in the process across multiple years.

Right now this in kept as a constituent attribute (custom field) that is all text driven, so there is no consistency across text information, dates associated with the attribute or to see who is connected to who.

I was looking for a "first class" field to have all the information in SINGLE location in the database, and since you can see events easily both in DBView and Webview, that was how I decided to track this information in an event. Having this information in a single location with dates and host-guest relationships makes it very easy for our development team to see how often the person has been involved in the award process. This information is critical for current relationship building as well as "institutional knowledge" for those staffers who may come on board in the future.

The event units are "nominator" or "nominee" and the nominee is connected to the person who nominated them by being their guest; as noted above a person may be involved in this process over multiple years, being either a nominator or nominee.

Also, right now this would not be a public facing event where people would actually register themselves, it's all "staff" driven coding. That's not to say that in the future we may want to try and make this a "self serve" function as NXT is built out.

For now my work around is to change the business rule setting in dbview, import the people, add their guests, then change the business rule back, all hoping that no one accidentally registers twice for an event for those events that may not be in NXT yet.

As always, thanks for seeking out clarifying information for our use of events.

Elaine

Hi Elaine!

Webview actually doesn't look at that business rule setting in database view, so today we always allow only one registration per person per event. Can you provide more info on your use case where you need to have a person register more than once? Are they buying more tickets? Are you trying to keep a grouping together?

Thanks for any additional info you can give!

Samantha McGuin
Principal Product Manager