Align database event Response field with NXT event RSVP status field
All the information in the Response field for Events in database view is lost in the conversion to NXT. This is true for the Status field in database Events as well. The RSVP Status field in NXT pulls only from the Registration field in database view. So "No Show" and "Canceled" table options for Response in database view appear as "Attending" in NXT. It would be helpful if Blackbaud could expand the choices in the database Registration field to include No Show and Canceled so that we can do an import to transfer the data to the Registration field so that it shows up in NXT. The database's Registration field is currently limited to Registered, Not Registered, and Do Not Register, with no ability to edit the table.
-
Anne Boudreau
- Apr 22 2021
- Reviewed: Voting Open
Before our organization had RE NXT webview we only had Database view. The "Response" field on event participant records in database view, to my understanding and my previous RE training by my managers, our organization would use this Response field section as the RSVP status. We have currently over 1,000 events, and to lose this historical Response information (where we listed their RSVP status), would not be helpful or wise. Database admins should at least be able to import this info to an event attribute or something else, so we don’t lose this information.
I can't understand why the options aren't the same in both versions. If I am running my queries in Database View based on RSVP status, then the option that is marked in NXT should be an option in Database view for me to query on. These fields should have the same values available if they are supposed to be used for the same information capturing.
I think the comments are spot on, aligning the DatabaseView and WebView would benefit of a lot of organisations for multiple reasons.
It's ridiculous that the information is not aligned. I delivered misinformation to my Board because I referred to the WebView on my phone and it said a donor had not responded when it was clear on Database view that they had.
This needs to be fixed
This definitely needs to be fixed. Need to be able to look at constituent records and see responses without having to open the actual event.
I also vote to fix this, it is a no brainer really.
I vote to fix this, I agree database & NXT status fields should align, it is difficult to keep good records if the details entered in database view events do not translate over to the NXT record.
I agree that the RSVP status should be aligned in NXT with the database. Particularly the field Declined in NXT should come across in the database as a Do Not Register, since that is the only option. For me, a declined and a do not register mean the same thing.
I agree that this is misleading. I vote to fix this.
Its is very misleading to see "attending" for people who are a no show. Especially when the other are marked "Attended". Those two terms look very similar and are easy to confuse.
We have taken to marking no shows as "Cancelled" in the registration field. This is not accurate but at least it switches the status label to "Invited" which is distinct from "Attended".