Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Attendees.csv -- Can I add more fields? | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Attendees.csv — Can I add more fields?

Attendees.csv — Can I add more fields?

Posted: February 7, 2013 at 2:19 pm

Viewing 2 reply threads


kolaughlin

February 7, 2013 at 2:19 pm

I am planning to import over 2000 past participants into our EE. I have downloaded the Attendee Batch Import Tool 0.1 and attendees.csv. The file includes these fields: Registration ID (optional), First,Last, Email, QTY, Event ID, Amount Paid, Payment Status, Price Option, Event Date, Event Time, Answers (optional). I would also like to include Address1, Address2, city, state, zip, and phone. Is it possible to just add these as fields and import them that way? This is an effort to keep our client’s database all in one place with all of the information they need.


kolaughlin

February 10, 2013 at 8:57 am

I have an update to my own question. I see now that the Answers (optional) field is set up for address, city, state and zip. That’s great! Even better if I could add and address2, another field (or fields) that actually has answers to 3 registration questions, and phone. Anyone know how to do this?


Seth Shoultes

  • Support Staff

February 15, 2013 at 12:14 am

Hi kolaughlin,

Sorry for not getting back to you sooner. Any extra fields will need to be added to the import script. That file is located in /includes/event-management/csv_import.php

Viewing 2 reply threads

The support post ‘Attendees.csv — Can I add more fields?’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server