Unable to attend option in Event Module

Aparna Krishnan

Hi there, 


Is there any way to mark unable to attend in RE NXT events module? We use OLX for our registration pages. 

I can only see options for Registered/ Unregistered/ NA and Invited/ Uninvited/NA. 

With the COVID19 situation, a lot of people are unable to attend the events, even after registering. 


Thanks in advance

 

Elizabeth Perron

Hi Aparna Krishnan‍,


I've noticed a peer has not answered your question yet and your issue seems to be technical. If you haven't opened a support ticket yet, I encourage you too.


If you still have questions, please scroll to the bottom of this community page to click on customer support. 


Please let me know if this is helpful or if you need something else!


In harmony,

Elizabeth

Blackbaud Community Team
https://community.blackbaud.com/community-managers


 

Samantha McGuin

Hi!


RE NXT Events does not currently support collection of "unable to attend" in webview. We have plans to include some new registration statuses of "Declined" and "Cancelled" that will release this summer. 


In database view, you may have options for this in either the user-defined fields of "Response" or "Status,"  depending on how your organization configured these fields for use. 


Thanks,


Samantha McGuin

Principal Product Manager

Alex BishopThorpe

Hey Aparna!


Really good question. As per Samantha's response above, this is not supported currently. We struggle with it too! Right now our workaround has been to set a "Participation Level" of "Declined Invitation".


It's not ideal, but it preserves the history. We expect we'll go back and amend this data once the new functionality is released to support Declined statuses.

Aparna Krishnan

Thank you all, I really appreciate all your feedback. we have decided to use Participant option for the time being 

Cassie Bartelme

Is there any timeline for all the registration statuses in database to display in webview? This post said it would release in the summer but we are well past that and still cannot see it. It is extremely frustrating that the database and webview options are not the same.

Samantha McGuin

Hello,


All of the Registration Status options have been repurposed in Webview at this time in the 'RSVP Status' field. This expanded feature was released in early September of 2020. Based on significant customer feedback, we have re-named and expanded the limited options available for database view's Registration Status field.

The full blog post explaining the changes is here. The pertinent information is as follows:


We decided to repurpose the Registration field in web view by changing the label to RSVP and replacing the existing “Registered” and “Not registered” values with a standard set of options:

• No response (default)
• Attending (previously Registered in database view)
• Declined (previously Not registered in database view)
• Interested
• Cancelled
• Waitlisted
• N/A (Not Applicable)

Is there a particular value you're using in database view that you're not finding a fit for in webview?


Thanks,


Samantha McGuin

Principal Product Manager

Elaine Tucker

Samantha,


Shouldn't Declined in webview be "do not register" in database view instead of Not Registered? Our default when globally adding participants in database is to have the default be "not registered". Once we get a decline, then they are marked as Do Not Register in database view.

We are slowly transitioning over to use web view only, but its a slow process.


Thanks,

Elaine

Samantha McGuin

That's a great input, Elaine. Through some surveys during our feature planning, we found some common majorities showing that - at least among survey respondents, 'Do not register' was commonly used for non-attending hosts or organization records, whereas "Not registered" was more ambiguous and had many different definitions to different organizations. Multiple of our webview statuses write to the "Not registered" option in database view. It sounds like our definitions are opposite of your current business processes from you global addition of participants in database view. The fact that DBV defaults participants to 'Not registered' does confuse the matter but was not something we could change.


It may be worth assessing if its worth the time and training to modify your global business process for adding participants to use Not registered instead of Do not register if you are looking at these records a lot in webview. I know swapping these around isn't an easy thing to do, but if you're in webview a lot it may be worth at least an assessment.


As always, thanks for your input Elaine!


Samantha McGuin

Principal Product Manager

Anne Boudreau

I don't understand why Blackbaud decided to ignore the database event field of Response. Declined is a Response, not a Registration. Canceled is a Response, not a Registration. Even No Show is a Response in a way, not a Registration. They have nothing to do with Registration, so why would we have stored the info there when the Event module was introduced in database view? I was told that the Response field and event Status fields couldn't transfer to NXT because they are user-defined tables. Yet you managed to recreate the Event Participation field, which also draws from a user-defined table. We can't use any of the event data in NXT because so much of it could be incorrect. The Event module integration wasn't well designed, or well explained. Even the field choices in NXT for RSVP status don't make sense to a fundraiser. Someone who calls to Cancel should not be looked at in the same way as someone who didn't bother to Show Up to an event. Even someone who calls to decline can be viewed differently from someone who didn't bother to RSVP. I also don't understand why you decided to shoehorn RSVP options such as Canceled, Interested, or Waitlisted into the database field for Registration. Why not match the tables so that info in NXT translates correctly to database view. This all leads me to believe that there was a rush to introduce Events to NXT without thoroughly thinking it through. So we're left with a choice of using database events, which don't translate to NXT or NXT events, which don't translate to database view. Definitely not up to Blackbaud's usually high standards!

Rachel Cavalier

One of my colleagues has come up against this discrepancy between RSVP in web view and Response in DB view - luckily, making sure DB view has the correct RSVP/Response data recorded is something that we can do after the event in this case and I will have the task of exporting the RSVP data from web view and re-importing it as Response in DB view.

Rachel Cavalier

Rachel Cavalier:

One of my colleagues has come up against this discrepancy between RSVP in web view and Response in DB view - luckily, making sure DB view has the correct RSVP/Response data recorded is something that we can do after the event in this case and I will have the task of exporting the RSVP data from web view and re-importing it as Response in DB view.

Coming back to this - we've ended up just going with DB view to enter data (primarily with my colleagues preparing queries for specific updates and then I would either global change or import the updates as there are a lot of participants).

We've used a combo of “Declined” response in DB view and “Do Not Register” for registration, which gives an RSVP of N/A in webview. The “Not Attending” total doesn't update on the Participants tile for the event record in webview (since that only counts RSVPs of Declined or Cancelled and not N/A) but I think this is something we'll have to live with.