Ensure the Max Number Available cannot be exceeded for event registration
When users are registering for an Event at exactly the same time, if they select an item that is almost full and they both register, they both get into the event which then exceeds the max limit. I would like for the system to prevent this from happening as we have Max #'s available for Items for a reason and need to adhere to these numbers.
-
Jamie Hardy
- Nov 2 2016
- Implemented
-
Mar 8, 2017
Admin response
This was released as part of the March 8 release. Thanks for your patience!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
Related ideas
Hi everyone,
This was clearly a mistake to handle this problem as an idea and I will be closing down this idea for voting. We expect that the Event Registration feature of onMessage (and onBoard) should enforce the maximum number of registrants. Previous testing has proven this to be correct, so we are currently researching this as a critical issue to identify what scenario caused this to occur on recent events. If you should experience this in the future, please contact support immediately so we can track the specific scenarios until we have them resolved once and for all.
Janet Wittenberg
Senior Product Manager, K-12
I agree...this can't be an 'enhancement request'. This should be serious bug fix.
Indeed!
IMHO, this should not be an enhancement request. This should be escalated and treated as a bug. We oversold an important event by almost 50 tickets in total. (Yes, the event is that popular.)
We use your event manager each year to sell tickets to this event and this is the first time this has happened. For this issue to not be on your priority list is shocking. By using your product, our Development Team and parent volunteers who chaired the event are now left to solve a very big problem, and contact 50 people in our community to let them know they didn't in fact get tickets to the event they registered for.
It's frustrating to learn that this issue was brought up by other users and not communicated to the schools who use onMessage. Had we known we would have used a different event manager, saving the built in onMessage product for lower stake events.
I had this happen with tickets to a high profile school event, where the last 4 tickets were essentially sold twice.This is an issue with in-demand events/registrations & does not give me a ton of confidence in the process.