Every organisation I have spoken to using RE uses 'do not register' as decline - we've just implemented NXT and this is a real problem that will mess up our events processes.

We need a way for Declined information to pass between NXT and database view. We need this 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 needs to be mapped to Do Not Register as it is the only distinct option in the hard coded Registration drop down. 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. 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.

Sorry I missed your reply Jerica! You won't be able to initiate a "decline" from database view, you'll only be able to code them that way in webview. Once coded as declined in webview, they'll show up in database view as "not registered."

Thanks, Samantha. How would you code someone in the database view so that they show up as declined in the webview? We always use "Do not register" as someone who has declined (and thus shouldn't be registered).

Hi Jerica,

"Do not register" in database view currently maps to "N/A" in Webview. Many organizations use this status for non-attending hosts (individual or organization hosts) and "declined" doesn't necessarily make sense in that context.

This mapping has been in place since the release of RENXT Events. I would love to hear more about the cases where you consider a "do not register" to be a decline!

Thanks,
Samantha McGuin
Principal Product Manager