|
Samantha
|
April 15, 2016 at 1:06 pm
HI!
Ok I was confused at first by the export in the attendance screen because rather than giving you a number 1 or 0 stating whether someone had attended that session, the number keeps increasing. Then I realized that it was because I had checked and unchecked and then checked the box again (to see what number meant they hadn’t attended).
The number does keep increasing, in fact if you check the box “off” it increases the number again. So if someone were checking people in, and checked someone by mistake and then checked them off, it would actually mark them as attended, and further, they would have a “2” in the checkins value (one for the checkin, one for the checkout) and checking them in again would bump that up to 3. That is not going to work for us, we do all our reporting around whether someone actually attended the event or not, and this basically removes any ability to do that. Unless I’ve got something setup wrong, which could certainly be the case.
In our instance, we have two types of events, one with one date/time and need to track attendance; and one with several sessions (date/times) which would each need to have attendance tracked separately. Pre-sales advised us that we could accomplish this by creating the required number of date/times, and the corresponding number of tickets and associating 1:1 the date/time to a specific ticket. For each of these, we have min and max set to 1. We only allow one person to register/attend with each registration. Is there something I should be doing differently so that we can achieve that setup and also have a report that shows attendance, and also allowing for check-in errors? Thank you!
|
|
Lorenzo Orlando Caum
|
April 18, 2016 at 8:05 am
Hello,
It keeps a running amount rather than a yes/no in the registrations csv report.
You could generate a registrations CSV report and then mark your guests as attended via Excel, Google Sheets, Apple Numbers or another program and then transfer than information into the check-in screen for Event Espresso afterwards.
—
Lorenzo
|
|
Samantha
|
April 18, 2016 at 5:11 pm
Keeping a running total is fine in the scope of what you guys are doing (keeping track of multiples, etc.) but it still does not address the fact that if I check someone and then uncheck them because I made a mistake, it should not show them as checked in and increment (now twice) the amount. How do you account for someone making a data entry mistake? This just can’t happen. If the box is UNchecked after being checked, it should DE-increment the number.
|
|
Samantha
|
April 21, 2016 at 8:43 am
OK I’m gong to say this one more time. If you are going to increment the number on each check-in, that’s fine, but if I UNCHECK someone…….that should DE-increment, NOT INCREMENT AGAIN.
How do you allow for any of your customers to make mistakes on the check-in process? I can’t believe that someone hasn’t accidentally checked someone in before.
Can this please be fixed? It makes no sense at all.
|
|
Tony
|
April 22, 2016 at 12:03 pm
Hi Samantha,
Thank you for reporting this.
We’ve been discussing this and we will need to alter the way in which the check-ins are displayed within CSV for this to work. Its not as simple as De-incrementing the current check-in value as it is a count of all check-in/out records within the registration spread across multiple datetimes. We could limit the query to only pull in check-in’s but that again would not de-increment the value if you checked out.
A single ticket can have check-ins across multiple tickets so we can’t base the field on a single value. We’ll need to break it down and apply check-ins to individual datetimes, showing if a the registration has checked ‘in’, ‘out’ or ‘never’ on individual datetimes in the CSV.
I have created a ticket for our developers to investigate this further however there is no quick fix for this currently.
|
