YES YES YES YES YES YES! We deal with dozens of events every month and would love to be able to export/import if there are multiple changes or import new events or 'catalog/master' events.

Registration types should be a separate table that you fill with event types and then select for each event or import correct reg type ID. We always have at the moment the same registration type and have to rekey the same type for EACH event. The data fields in the event even reference a registration type ID with the registration type date but there is no 'master' as such or any way to pick from existing.

We can import/export or edit via API most things, events should be just as much so.

PLEASE PLEASE PLEASE PLEASE

yes! to transition to **, i'd like to import as much information from the patchwork of solutions we're using now. i'd love to be able to import event information.

I am happy to build a screen-scraper to automate this kind of import. (My organization wants to bring a 10-year history of prior events as part of its transition to WA.)

The description editor has stumped me. Could you please tell me the Id of the element that holds the description text?

Thanks.

Same here, for other reasons we have to maintain a separate events calendar which includes a range of event types. It would be very handy to be able to point our 'WildApricot' events calendar at a feed from our events calendar and let rip.

An import of events should contain all required information to create or update the events. Registration type should be one of the required fields. For many of my events there would be no registration, these are information only calendar events. Other events allow only 2 registrations while others have higher limits or none at all; for example all members my register for the end of season party.

I think that registration types should be predefined within event managment so that the import need only refernce a specific type code.

Thanks for your comments.

Let me ask you guys - how would you ideally deal with registration types when events are imported (one event can have multiple reg types = ticket types)?

Our club post 30 to 50 evetnts per month. I suggest you look more closely at the business requirements of your existing customers. We could use an import feature as well.

The ability to import events will be crucial to my decision to purchase Wild Apricot for the 3 organizations I'm working with!

One organization uses events to assign referees to meets, there are about 60 per week.

Another uses events to for customer appointments, there are about 50 per week.

And the last is a large swim team that uses events for practices, meets, and other team events, there 20 to 30 per week for this.

Yours truly will have to enter each event manually? I don't think so. Please, please, please put this option in place. Honostly, is it really that difficult?

I could really use this feature. We are going to have 100 or so events every quarter that will need to be added. It is taking hours to create them manually. It also leads to lots of errors. Since it is such a long process you tend to get distracted.

Please look at imports for events.

The ability to import events needs to be pursued! We have an average of 10 events per month. I have 20 events to add today and I don't look forward to all the time it's going to take. Copying is not an option for any of these events.

Speaking of copying, the copy event feature is very slow and not user friendly. It would be helpful if I could filter the events in the copy from window. With the large number of events we have, I may have to scroll through over 100 events.

Thank you for your consideration!

Guys, most of our users typically hold 1-2 events/month so it does not make sense for us to develop an import facility for events at this time, sorry.

I will still keep this thread on the wishlist and would appreciate comments from other users.

We really need a way to import event data (as text), so we do not have to enter each event separately. All of our event data already exists in our database. Currently, we have to print that out and have someone manually enter each on into wild apricot. Would help work flow if I could export the event data into a text file that could then be read/imported into wild apricot.