Event registration field from membership fields
Currently only Common membership fields can be included on the event registration form, but I would like to include custom membership fields on the event registration form as well.
Example: Certified and Associate members have a membership number from our national organization, but other members do not, so it is not a common field for all membership types.
When creating workshops, I want to include the membership number on the event registration, but have it automatically included from their membership field instead of creating a custom field for the event to have them type it again.
Steve Smith commented
This feature add will provide added value to registration reports. We have membership field specific data that can not be common data due to different membership levels. We wish to be able to pull registration reports to use member specific data when printing event credential badges. Thanks
I want to be able to add emergency contact name and phone number in event registration information - but I will have to make them common fields for all contacts. The problem with that is we make emergency contacts mandatory for riders - but it's not appropriate to make it mandatory for contacts.
Trent Andreas commented
We are a youth based organization. Normally the parent will register the child for an event. We are having to jump hoops to have the Child's name appear on the registration. If we could customize the notifications (and event the registrant list) it would be far easier to register.
I have this exact problem. 400 registrants registering for 12 events per year. We are also keyed off a membership number that is not common among all contacts.
The typos are killing me.
Malcolm de C commented
I fully support the ability to pull data from custom fields rather than it having to be entered. Clearly it wouldn't make sense to use a check box approach for every custom field but it should be possible when adding a new field to have the option to select an existing custom field rather than defining a new field
One of the custom fields we have is the certification number for our members who are licensed clinical professionals. We need that to provide CEU certificates. Including it in the event registration form allows us to keep that information updated. It is very inefficient to create a separate field for it just for that event, because then we have to compare it to what was already in the system and sometimes they don't match, etc...
Walt Bilofsky commented
This would help us too. When our boating members register for a cruise, they need to enter their boat length and width. So I had to make those common fields instead, which makes no sense for most nonmember contacts.
Why not just pre-populate any registration form field whose name matches either a common or membership field with the contents of that field, if any?