|
Amy Lepre
|
October 16, 2017 at 11:36 am
On our event we have several tickets that one person can purchase in the same transaction. I just realized, though, that when a user selects more than one item, they are then entered into the event registrants as a separate contact for each ticket they purchased. This creates a lot of confusion when trying to count how many registrants we have for an event, both in the EE console and when we export out the registrants (have to merge the two contacts, or delete one, etc. Is there another way to have users purchase more than one item without creating multiple records?
For more information about our use case – we have one event where users can purchase a ticket to the main event and/or tickets for meals. Additionally, there are multiple main event tickets based on date, as we give discounts for purchasing early. We also have different combinations for the main event and the meals – they can choose main event only (2 different prices based on date), main event plus dinner (as one ticket, with 2 different prices based on date), main event and lunch & dinner (as two separate tickets – one for event, one for meals and the main event has 2 different prices based on date). You can see the registration here: http://oaregion7.org/events/2017convention/
|
|
Tony
|
October 17, 2017 at 4:15 am
Hi Amy,
I just realized, though, that when a user selects more than one item, they are then entered into the event registrants as a separate contact for each ticket they purchased.
Separate contacts or registration?
Each ticket will create a separate registration on the event for each ticket selected but all of those registrations will be set on the came contact (with your event setup).
So to confirm do you mean you have multiple entries within the registration list? Like this – http://take.ms/yLDi2
Or contacts, like this – http://take.ms/vXfcqy
Is there another way to have users purchase more than one item without creating multiple records?
If it’s the registrations mentioned above then no you can not prevent a ticket from creating a new registration.
|
|
Amy Lepre
|
October 17, 2017 at 7:00 am
It is multiple registrations, not contacts. How can I view contacts for one event instead of all events? What if I used something like this: http://aparnascodex.com/downloads/price-modifier-for-event-espresso-4/ Would that give me 1 registration per person?
|
|
Tony
|
October 17, 2017 at 7:24 am
Would that give me 1 registration per person?
Per ticket.
You will always have 1 registration per ticket selected.
It is multiple registrations, not contacts. How can I view contacts for one event instead of all events?
Contacts aren’t linked to events so you can’t.
Registrations are linked to the events, so you can view the registrations for a specific event. To do that go to:
Event Espresso -> Events -> {hover over event} -> Registrations
That will show a list of registrations on the event you hovered over.
Is that what you are looking for?
|
|
Amy Lepre
|
October 17, 2017 at 7:33 am
When I go to the list of registrations, I have what I consider duplicates because it’s the same person from a single transaction/registration who selected two tickets, say one for “Convention Only” and one for “Lunch and Dinner”. What I want is a list by person/email address with their total amount owed and paid. Right now I can only get to this by exporting out the registrations and manually cleaning it up in Excel.
|
|
Tony
|
October 17, 2017 at 8:07 am
When I go to the list of registrations, I have what I consider duplicates because it’s the same person from a single transaction/registration who selected two tickets, say one for “Convention Only” and one for “Lunch and Dinner”.
As far as EE can see, a ticket is a ticket.
There is a 1 to 1 relationship between tickets and registrations, every ticket equals a new registration. You can’t turn that off or remove it so if your users need to select multiple tickets they will always show as ‘duplicates’.
What I want is a list by person/email address with their total amount owed and paid. Right now I can only get to this by exporting out the registrations and manually cleaning it up in Excel.
You can’t export by contact, but the rows within the CSV are filtered so it should be possible to check if a registration is not the primary registration and remove the additional rows from the CSV before its sent to the browser, although you’ll need to remember the export is doing that should you need full details in the future.
Would that work?
|
