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 Exporting Attendee Data to Excel doesn't incl. Registration IDs | Event Espresso - Staging Server
I tried to search for help on this topic, but search results kept giving me closed topics on the old support forum, so I’m starting my own thread about it.
For some reason our attendees’ email addresses (and other info) have not been importing into MailChimp, so now I need to add the 55 people who have already registered. (Although I do need to first figure out why they weren’t importing immediately upon registration, since I have that setting turned on in the Event Registration Detail.)
However, when I exported “All Attendee Data” into Excel so I can import to MC, it’s giving me “4e5b01bfcbaf12.97630320” for their Registration ID # instead of something like “26-522df519cee1d”. A support conversation from Feb 2012 here (http://staging.eventespresso.com/forums/2012/02/registration-id-2/ ) indicates that this would be resolved in the “next major release”. When will that be?
Oops, totally my mistake! I realized that the ID number IS included in the Excel file… it’s just right-justified in the Excel column next to the really long ID # and I didn’t even see it there until I looked again tonight. My mistake – sorry!! (Not sure how to delete this whole topic.)
Viewing 1 reply thread
The support post ‘Exporting Attendee Data to Excel doesn't incl. Registration IDs’ 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.