|
What is the best way to implement RSVP list for SharePoint? How would I limit the number of RSVP for an event? Do I still need to use InfoPath for UI and Logic? Never implemented RSVP event list before and I would learn how you have it done or setup. Thanks |
|||
|
|
|
You could still use a list, just use some other additional pieces. You could have a list that contains the event and the limit, a column for number registered, and a column for available spots (which is the limit less the number registered). Then you can simply go in and add a link to register (the registration is contained in another list) when you enter this information, you can have a workflow created that will add to the number registered for the event. You can set some conditional formatting by making the registration link not available when the number of available spots is equal to zero. Since the lists in 2010 are XSLT List Views, you can easily add this conditional formatting to the list view. You can also add a link that filters the registration lists to show only those who are registered by adding in a link to that which would include the filter query string in the url. The workflow could be a simple SharePoint Designer workflow. You could even get fancy and create a mashup, or use the preview pane to show the registered users below the event details by creating a custom display page. |
|||||
|
|
Being a complete InfoPath-phobe, I'd opt for using just a standard list, with the columns you need, and the logic for checking the limit of RSVPs implemented inside an Item Event Receiver, which handles ItemUpdating. You could put the configuration of what RSVP list has what limit into another list (columns for this config list could be, for example, URL to the list being configured, and a number for the maximum RSVPs). Everyone invited to the list has an entry in the list, they go into the list (a view filtered by the 'to' address, maybe), edit their entry to set their RSVP status. The event receiver will check to see if they've set it to 'accept', then count how many 'accepts' have been made so far, and compare it against the value stored in the other list (the config list). If the number exceeds, they can be redirected to a helpful error page and the 'Update' event cancelled. This might not be the best way to do it, but it will work in SharePoint Foundation/WSS, can be deployed to the Sandbox, and doesn't rely on any forms development. Just some C# code. |
|||
|
|
You could use this golden oldie! http://spforsquirrels.blogspot.com/2008/03/follow-up-training-classes-scheduling.html |
|||||||||
|
