Are you referencing to http://forums.wildapricot.com/forums/308920-archive/suggestions/8835160-ability-to-exclude-some-common-fields-from-a-parti ?

Yes in general - but before deleting any field do not forget to export all contacts otherwise you will loose data in this fields forever.

You make export, delete fields and when importing back setup this columns in import fields mapping as new field in contact database.

Evgeny -

we have a need to change 2 membership fields to common fields. will the procedure be essentially the same? i would guess that we would delete all common fields as well as the 2 membership fields that we want to be common fields and then follow your process. is that correct?

thanks in advance -

Kim P.

Donation form is affected as well.

I'd like to keep focus in this thread on event registrations and speak about membership form in another (new) thread. Could you create a dedicated thread for membership and describe all details there? This would help us to understand the whole picture and we might to come to a different solution in the end.

Yes, if this is an easy solution, I am in favor. It would work for me. Is it possible to add this for the new member form, as well as event registration form? Judy

I just started following this thread because I had some of the same questions. Your suggested solution would work great for me!

Cathie

Interesting - instead of doing a big change that is in our minds, can we just make the same for event registrations as we did for subscription form?

I mean that on event details page, registration form tab we now show only event specific fields - and give a small notice that all common fields are to be added automatically (and this is the root of confuse and discussion). Instead of the notice we will show list of all common fields with checkboxes (look into subscription form functional page settings for example). Admin can uncheck the fields he does not want to show on event registration form (except e-mail - it is always shown, this we cannot avoid for now).

This is a quite small change - would it work? Any comments are welcome.

Correction: no need to delete your contacts.
* make export of all contacts
* delete common fields
* DO NOT DELETE CONTACTS
* start import - do not even add new fields before that
* on mapping screen, select only member id field and fields you deleted before. For those fields set them up as new member fields and defined required type of the field
* import - this will add new fields into membership form and update only these new fields on contacts Should be quite easy.

Judy,

The whole idea behind 'common fields' was that they are common for all contacts and thus are present on all forms.

We are now seeing that this model is not flexible enough in a number of cases so we are thinking about changing it. The first small step was with the email subscription form where we allowed customization of common fields.

This is something we will be working further on - though some time away.

The only way to change common fields into membership fields is exactly how you described.

Yes, all of our events (except our annual general meeting) are open to the public, it's just that members can go for discounted rates.

And thank you, Judy, for pointing that out about the fields! I hadn't even thought of that, but I think you're right.

WA support, is there a way to change common fields into membership fields without affecting the data? Or would I have to export the entire database, delete all the records, delete the common fields, add them as membership fields, and re-export everyone?

My event is a members only event...sounds like your event is public? Maybe that is the difference.

Well...how WOULD you move fields from common to membership fields with their existing values? That is a question I would like to know!

Judy

That's strange, Judy, because that didn't work for me. Under common fields I have street address, state, postcode, etc., and they're all marked as "no access", and yet they do come up on my event registration form, both when I was logged in as a member and when I was not logged in. (They're set for mandatory, but other, non-mandatory common fields such as phone number also come up, so that can't be it.)

The problem with this is that I don't want to have to ask non-members who are registering for our events for their street address, since just their email address will do.

I'm realising I may have to just move the address stuff from common fields to the members-only fields, though I don't yet know if that will affect anything else for us down the line. (ie cases when we want someone's street address for something besides event registration, if they're not a member).

The ability to pick and choose which fields show up on an event reg form would certainly be handy, at any rate.

I just discovered a few things that were not apparent until I had actually finished setting up an event registration form, enabled the registration, and then logged in as a member to test it. The common fields that are designated on the database as "Others Access" - "No Access" DO NOT appear on the form. This fixes my immediate problems.

Also it appears that the fields you set up on the event registration form are specific to that event and so don't appear on the general screens, which is also good for my purpose.

I apologize to the community for being alarmist in my previous message.

Judy

I have to agree with Judy here -- there are different details we want from people depending on what they're registering for (membership, events, announcements, etc). Can this go on the wishlist?

This renders the on-line event registration useless! We need different fields for different events, and some of the common fields are not used at all for events.

I am very disappointed that we can't use this system for event registrations, which is one of the reasons we started with Wild Apricot!

Judy

Joel,

Sorry, all common fields are currently always present on the event registration form (as well as on the membership application form and donation form)