I'll add my vote to this feature request. We have an annual conference and attendees choose which workshops to attend. I have a use cases where I would like the ability to select which form fields appear for which registration type.
We have a three day conference but offer a "Friday only" rate. I want those registrants to only see and select their workshops (pull-down fields) for the Friday sessions and options.
To implement, I see an option with each form field where we can select which registration types that field applies to.
I have a case for needing to import event registration information. We have 95 persons registered (so far) for an event. We added a new registration field. I need to update that field with information I have.
To update 95 registrations, I have to go into each one, click edit, set the field, Save, Cancel invoice update, click Back, click Next. And do this 95 times. We typically have 250-300 registrants. This manual process is too time consuming.
I would like it if I could export registrations to XLS, make edits, then import back to the event.
Collecting comments now.
We just launched integration with Integromat platform, which helps to build automated workflows. We also provide several templates for quick start, and one of them allows to send birthday emails.
You can try the integration by this link https://www.integromat.com/en/integration/2274-happy-birthday-to-wild-apricot-members
3 votesDennis shared this idea ·
I have just run into this issue with my client. They have individual members and organizational members. They do not want to display any personal information for the individual member listing, but do want contact details for organizational members.
I would have been great if I could just turn off access to the profiles with a simple check box. I can still include the minimum info that they want to display for individual members by what I select to display in the listing columns.
Without this feature I have to export all individual members, set the permissions for their contact information in Excel, then import. And then I have to change the permissions on fields for all new individual memberships. That's 30+ minutes of work and plenty of opportunities for human error.
This could be one of those sleeper features that folks don't bring up much, but would like to have.
Thanks - Dennis
p.s. - I used the script posted earlier and it worked - the member names look like links but the link goes nowhere.
We have a similar organization as alexyaronyc. We gain most of our members by offering discounts to our conference and training events. It would be quite an advantage of our event attendees could join and register with a single payment.
That said, we would need the following:
* Simple. A shopping cart could work if the workflow is obvious for non-tech users. WA does a great job on user flow and that would be key for this as well.
* Separate accounting. The user should be able to make a single payment (single invoice), but internally, there still needs to be two invoice line items that each map to membership & event records.
* Event pricing based on cart contents. If the user includes a membership in the cart, then they can qualify for the lower priced member price for the event.
* Hum - not sure how how you would handle the above bullet if the membership requires approval but the event registration doesn't. You smart guys will figure it out ;-)Thanks - dseger
Please review our current proposal: https://docs.google.com/presentation/d/123zVAgAcSLQb02vC6v8zj-6qoEAEW56cJ-3ioqv5WEc/pub?start=false&loop=false&delayms=3000
This is a feature that I would like. Our users/members are not sophisticated enough to subscribe to a different service like feedburner. I would suggest a "subscribe to this blog" button available on the blog functional page and widget. Then if a logged in member clicks the button, they are subscribed. If they are not a member, they can provide info to become a new contact.
That would work well for us.
Keep up the great work Apricots!
I'm casting my vote for this feature - and just as Apricot Kernel described it. I would prioritize it as...
* allow admin enable/disable password strength setting (to a default strength)
* admin can set password strength (maybe just 5 preset settings, with none being the least)
* lockout for 10+ failed login attempts
In all cases, enforce only for new contacts or password changes. Don't affect existing users.
I'm casting my vote for this this enhancement. We have five different memberships with different event pricing. And now our Board wants to discount pricing to some other special groups. This can be accomplished by creating registration levels for each group/membership level. But it results in a long (and confusing) list of registration options.
The membership discount code works great. If it could be ported to events, you would solve another issue for us.
Keep up the great work!