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
EE4 Exporting Data to cvs/excel file | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium EE4 Exporting Data to cvs/excel file

EE4 Exporting Data to cvs/excel file

Posted: April 14, 2014 at 8:47 am

Viewing 3 reply threads


Justin Harris

April 14, 2014 at 8:47 am

In EE3, I had the option to export all registration info to an excel file; however, i can not find that option in EE4. Is that not possible anymore?


Anonymous

April 14, 2014 at 9:47 am

Hi Justin,

Currently you can do this for each event within EE4.

If you go the registrations for your events, you can do this a couple of ways. Either through the Event editor then registrations, or Event Espresso -> Registrations -> Check-in tab. Select your event in the drop down and click Fliter.

They’ll you’ll find the ‘Registration CSV Report’ button http://take.ms/JrODJ

Does that help?


Justin Harris

April 15, 2014 at 10:56 am

I have like 200 different events…? I have to go through each different one? Is there no export all registration information button like there was in EE3?


Lorenzo Orlando Caum

  • Support Staff

April 17, 2014 at 11:59 am

Hi there Justin,

Unfortunately there isn’t a bulk export option for all event registrations at this time. I’d added this to our feature requests so it can be considered for a future version of Event Espresso.


Lorenzo

Viewing 3 reply threads

The support post ‘EE4 Exporting Data to cvs/excel file’ 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