NetCommunity Registrations - Best Practices

Options
Registrations for NetCommunity never seem to end up on the participant record the way I want them to appear: Registrants registering themselves not as the primary registrant, but as their own guest and other issues. I always seem to need to tweak the participant record. To keep up with this, I make sure to add the participation type (e.g. Donor, Honoree, Attendee, Guest, etc.) and the status as Paid to each record only after I tweak it. That way I can go back and sort by participation to see which records I have yet to update. 


Does anyone else have any best practices when it comes to NetCommunity Registrations?
Tagged:

Comments

  • Amanda Downs:

    Registrations for NetCommunity never seem to end up on the participant record the way I want them to appear: Registrants registering themselves not as the primary registrant, but as their own guest and other issues. I always seem to need to tweak the participant record. To keep up with this, I make sure to add the participation type (e.g. Donor, Honoree, Attendee, Guest, etc.) and the status as Paid to each record only after I tweak it. That way I can go back and sort by participation to see which records I have yet to update. 


    Does anyone else have any best practices when it comes to NetCommunity Registrations?

    Hi Amanda! That sounds a lot like what we do. We struggle with everything (like meals) going into attributes instead of the meal choice area and need to tweak everything anyway so it works for us... though we wish there was a better way. I attached the policy I wrote for each of the tables on the participant record in case that's helpful to anyone. We use 'registration status' to track if their record has been updated or not. 

  • Having the non-registered participant pay and then having a duplicate registered guest, I am thinking this is a user error by the visitor on the website. But I was just testing it, using the Event Registration Part and the Event Registration Part - Classic, and cannot figure out how a web visitor could do that. It only happens once in a blue moon for us. Most come in correctly. I go in and fix the non-reg participant and delete the guest, making sure the payment is moved to the participant record linked to the constituent.  I don't like that it puts the payment on the non-constituent participant records instead of putting the payment on the constituent.  That's how we do it when we put checks through batch for events.  All the money goes on the payer's record.  We also use attributes for a few other things, like seating requests.
  • I think this thread specifically addresses this problem -- and it was turned from a forum post into a suggestion:


    https://community.blackbaud.com/forums/viewtopic/348/18166?post_id=60995#p60995



     
  • Thanks Angela for sharing this!

Categories