Importing via csv / Updating via csv import / series of events

[Saskia Lund]

Hello there!
I do have a few questions regarding the integrated csv import functionality:

1. When importing new events with multiple event dates (recurring event), how would I have to set up the csv file?
2. Does each event occurrance need its own row?
3. Is this supported by csv import? From the description it seems that we can import single events only, but not a series of events.
4. How would I update an exisiting event via csv import? Is this supported?

Fast answer appreciated!

Thank you!

[Victor]

 

Hi Saskia!

Thanks for reaching out to us! Let me help you with this topic.

Unfortunately, the import functionality does not currently support importing recurring events as such. Though, they can be imported as single events, so if you have a recurring event, each instance should be in its own row.

You can update existing events via a CSV import. You can adjust import settings by going to Events > Settings > Imports tab.

As a reference, let me point you to the following article that shows the process of importing from a CSV file > https://theeventscalendar.com/knowledgebase/importing-data-from-a-csv-file/. Also, you will find CSV file examples in the following article > https://theeventscalendar.com/knowledgebase/csv-files-options-and-examples/

I hope that helps. Let me know if you have any follow up question and I’ll be happy to help 🙂

Best,
Victor

[Saskia Lund]

Hello Victor,

thanks for your reply.

Well, that is unfortunate, as we are exclusively using recurring events on our site. And it is somewhat of a nightmare managing those events manually, as backend page loading times have increased so much in more complex events.

Thanks for pointing me to those 2 articles. However I already found them before I started this thread. Because these pages did not answer my questions, I started this thread.

Importing Tickets is also a nightmare to be honest.
It plainly doesn’t work at all. The SKU field for example is not being offered by the import tool, despite explanation in above mentioned info pages.

Please answer these questions, that I have asked before (about a year ago) in this forum:
WHEN will recurring events be fully implemented?
WHEN will import be available for recurring events?
WHEN will tickets be supported as they should by recurring events? One ticket pool is a nightmare, even though I am using several custom coded workarounds and modifications to be able to access attendee data more conveniently.
WHEN will the attendee info be saved to database in their own datasets (with own IDs and relation to their individual ticket and woocommerce order), instead of that catastrophical solution via “update order item meta” in WooCommerce that you guys built there?

Thanks!

• This reply was modified 8 years, 3 months ago by Saskia Lund.

[Victor]

Hi Saskia!

Thanks for following up with this. I’m sorry to hear that you’re having trouble managing your events. Let me try to help you with that.

The slowdown in performance for your site’s backend could relate to a variety of variables. Recurring events do take some more time to load, but if you are experiencing a significant difference in the time it takes to load a particular recurring event, please let us know about it and share a screenshot of the recurring settings as well as a link to it.

The SKU field for example is not being offered by the import tool, despite explanation in above mentioned info pages.

I have just tested the ticket imports via CSV and it shows the SKU as a field to import. If this is not showing up for you it could be a conflict somehow, in which case I’d recommend going through the testing for conflicts guide. If the issue still persist, please open a new topic for this so we can help you out with the troubleshooting.

WHEN will recurring events be fully implemented?
WHEN will import be available for recurring events?
WHEN will tickets be supported as they should by recurring events?

We are in the process of thinking new ways to implement recurring events so that they can support recurring tickets, but at the moment, we don’t have an estimate for when this feature will be available. In the meantime, the recommended process would be to break the event out of its series and then create tickets for it.

Importing recurring events is not something that is currently under development, but I could find this as a feature request in our User Voice > https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/17434264-add-csv-recurring-import-to-aggregator. I suggest you add your vote to it so it can be taken into account as a new functionality.

WHEN will the attendee info be saved to database in their own datasets

I’m not aware of such change to be made in Event Tickets. Do you think this is something that will improve how the attendee info is handled and saved in the database? Please let us know more about it.

Let me know how that goes and if you have other questions.

Best,
Victor

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts