Unable to use Capacity field in Event record to define the maximum number of Registered participant only

Currently the Capacity field in Event record defines the maximum total number of participants for an event.

Would like additional settings in Config - Business Rules - Event options so that Capacity reached calculation is based on Registered Participants and Registered Guests OR it can include Do Not Registered Participants/Guests OR it can include Not Registered Participants/Guests - provide tick box, if tick include in calculation.

This is an existing suggestion under http://www.blackbaud.com/kb/index?page=content&id=BB733129

  • Guest
  • Jan 31 2013
  • Attach files
  • Apryl Bundy commented
    April 21, 2022 20:31

    Every year we have an issue with this when we hold a golf tournament. We have one big event setup in RENXT - the golf tournament, but we need to limit the number of hole sponsors we can take to 18. I cannot believe this "Cadillac" of a system can't limit the individual prices on an event. If we choose to put in a capacity of 18 then we limit the number of people who register to play to 18. Is there a work around besides us manually keeping up with how many people register to be a hole sponsor and then when we hit 18 remove it from the page?

  • Guest commented
    March 17, 2016 23:36

    This is really a problem for me now and could be a show-stopper for using online event registration for some other things.

  • Guest commented
    March 17, 2016 23:36

    Hard to believe this isn't already included in the functionality - surely there are many other organizations that have events structured similar to ours with different ticket levels and different capacities for each.

  • Guest commented
    March 17, 2016 23:36

    Jennifer - this suggestion is not about different ticket levels - that would be a good suggestion too.
    But this one is simply about the way the capacity field calculates the number. If I remember correctly it is includeing toward the capacity people who are in the do not register category (like vendors, etc.)

  • Guest commented
    March 17, 2016 23:36

    Please fix this! Right now, if I invite someone and they do not attend, they are counted toward event capacity (even though they are marked "Do Not Register" and "Not Attending"). Having user-defined settings for the capacity calculation would be great, but as an interim solution, even just making it assume that only those marked "Registered" count toward capacity would be an improvement.

  • Guest commented
    March 17, 2016 23:36

    Functionality tied to the event capacity (such as the automatic "sold out" deactivation of BBNC event registration pages tied to RE events) is defeated as long as any participant records may include those who will not actually participate. This is really functionality mismanagement within RE and RE/BBNC integration that needs to be addressed.

  • Guest commented
    March 17, 2016 23:36

    It would be great if you could adjust this in Configuration but even more importantly the same recognition needs to be carried over the Event Registration Forms in Net Community. Currently the "Sold Out" function in Net Community calculates capacity by Registered guests only where as the Events Module calculates maximum capacity using Registered, Not Registered and Do not Register. Trying to manage an event that actually has to sell out between the two places is difficult and risky. We had to ask our golf course to accommodate 8 more people than the course normally allows for our outing because of the disconnect.

  • Guest commented
    March 17, 2016 23:36

    it would be good to be able to calculate the actually registered attendees toward the capacity total and not include all registered participants. It does skew the online registrations. As it stands, we have to keep adjusting the capacity each time we have a Do Not Register to be sure we sell the maximum tickets available - but with that being said, there is always the risk of overselling as well. So this would be a good think to have fixed in RE