|
smallfryart
|
January 10, 2016 at 10:40 am
I have created an event with multiple date times along with a ticket that has the # date times set to 1. If a customer purchases 1 of these tickets they then show up on the check-in page for all of the dates for that event. Once they check in to a date, they STILL show up on all of the dates. Is there a way to hide registrants that have already maxed out their # of date times for their ticket on date-times for which they do not already have a checkin record? Otherwise, the list of attendees to sort through will get very long on all the date times and the only way to know that the registrant has maxed out there ticket is to try to check them in.
|
|
Josh
|
January 12, 2016 at 9:13 am
Hi there,
I’m not 100% sure how the tickets are being set up, so may I ask does each ticket get assigned to one datetime or does each ticket get assigned to many datetimes?
|
|
smallfryart
|
January 12, 2016 at 8:01 pm
The ticket is assigned to ALL of the date times.
Here is what I am trying to accomplish… My wife and I run an art studio for kids and every saturday we have an open studio for $10 per kid. We’d like to sell a ticket that is good for 2 admissions to any date. We would use event espresso’s “check in / out” feature on each saturday to manage whether or not to let somebody in.
In my testing though, I noticed that if Suzie Customer buys a 2-pack ticket, here is what happens:
On Saturday 1 I filter the checkin page to my event for Saturday 1’s date and see Suzy as a valid and paid registrant. I check her in and it works.
On Saturday 2 I filter the checkin page to my event for Saturday 2’s date and see Suzy as a valid and paid registrant. I check her in and it works.
On Saturday 3 I filter the checkin page to my event for Saturday 3’s date and see Suzy as a valid and paid registrant. I check her in and it fails with the following error:
The following errors have occurred:
Check-in denied because number of datetime uses for the ticket has been reached or exceeded.
The given registration (ID:55) can not be checked in to the given DTT_ID (51), because the registration does not have access
Suzie Customer’s check-in status was not changed.
This isn’t very user friendly.What I’d prefer to see is that on the third day, suzie isn’t even shown as a valid registrant. Or at least that she has a special color bar indicating that she has maxed out her checkins based on the tickets she has purchased.
|
|
smallfryart
|
January 22, 2016 at 11:20 am
Any thoughts on this?
|
|
Tony
|
January 26, 2016 at 10:00 am
Hi there,
Thank you for the explanation, it makes sense now.
I have created a ticket for some feedback from our developers on this but currently the check-in total and check-in limit values are only evaluated when a check-in is attempted. This means there are no values to compare against within the table to use for a status strip for each registration so for either of the 2 options you mentioned above the query will need to be altered to pull in the relevant details.
We will update this thread with any news.
|
