Map NXT RSVP Status "Declined" to database view "Do Not Register"
We need a way for Declined information to pass between NXT and database view so that our admins can use either view and get accurate information for reminders and follow ups.
Given that RSVP Status from NXT has been mapped to Registration in database view, "Declined" from NXT needs to be mapped to "Do Not Register" as it is the only remaining option in the hard coded Registration drop down other than the ones indicating they have not yet responded (Not Registered) or they are coming (Registered).
Currently everything Declined from NXT looks the same as no response to us in database view (Not Registered) and Declined that has been updated in database view looks like no response in NXT (N/A). This means the information is not flowing between the views and then means we have no single source of truth for Declined information for our events.
The number of participants who are non-attending hosts would be far outnumbered by the number of participants who have said they are not coming and therefore need to be excluded from reminders.
The current mapping needs to be changed so that Declined information can be distinguished in both NXT and database view.
-
Natalie Townsend
- Jun 18 2021
- Shipped
Related ideas
Hi Natalie,
Since Declined is something that can only be set via Webview and there is not a unique system value in database view's Registration field to map to, we felt it best that when Do not register is recorded in database view, N/A was the best value since we can't tell if the intent of the Do not register is actually N/A, Declined or Cancelled. Many organizations use Do not register for non-attending hosts or organization hosts as well, so we can't count on Declined being the actual intent.
I would encourage you to use webview when you are entering in declines so that it can be accurately reflected. If how a Do not register writes into webview continues to be a problem for you, please create another Idea and we'll keep an eye on the feedback to see if we need to continue digging on this.
Thanks,
Samantha McGuin
Principal Product Manager
This is a great improvement, thanks Samantha. Now when admins update participants in NXT as Declined or Cancelled in NXT, this is distinguishable in database view as Do Not Register. This will mean admins can now update all responses in NXT which is great news.
However, I have just tested updating as Do Not Register in database view and this is still appearing as N/A in NXT which means the response is unclear in NXT for these participants. Are there plans to amend the mapping in the other direction as well? It should default to Declined in NXT if updated as Do Not Register in database view as this will be the most commonly used option. If it's actually Cancelled instead of Declined, it can always be updated in NXT to reflect this extra level of detail and will still appear as Do Not Register in database view.
For our last webview events release of the year, we've made a change to how the RSVP values of "Declined" and "Cancelled" maps to the Registration field in database view. When an admin changes a participant's RSVP status to either Declined or Cancelled, starting today this will write to the "Do not register" value in database view. This will be noted in today's What's New.
Thank you Natalie for bringing this to our attention, and thank you voters for making sure we knew it was important enough to change. We don't like to change mapping often, but in this case we got this one wrong. Your votes and explanations of the problems this was causing let us know this was important enough to do.
Samantha McGuin
Principal Product Manager
110% agree with you!!! This is so frustrating. RSVP Status should be the same as Registration Status. NXT and RE should speak to each other.