nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Recording Event RSVP's - Fields don't match across database and NXT view

Helen Bowen

We recently moved to RE NXT. When recording event RSVP's the fields don't match the database view (Response/Registration) so I can't get the RSVP information to show the same info on the database view and on NXT.

Whats the best way to record RSVP's and get all the info you need?

Find more posts tagged with

Events

Comments

Alex Wong

@Helen Bowen
Hi, I'm not sure what you mean by the “RSVP” field, are you talking about event record or participant record?

If you can provide some screenshot that will be great.

Also, note that RE Database view has the ability to “custom” label some field in some record, while RE NXT webview does not take those custom label into consideration. Not to mention there are name/label/terminology changes that exist even when there were no custom label change on your org's part.

Adrienne Baumann

@Helen Bowen Hi Helen - What works for me is opening the Event in NXT; click on “Work with Participants”; click “Add”; then fill in the prompts from there. (Being sure that you have added “participation levels” when creating the event.) I use this for RSVPs - linking their registration is another step. I hope I fully understood your question and that this helps!

Rachel Cavalier

@Helen Bowen
We came up against this last year, IIRC when you mark someone in webview as RSVP Status “Declined” it puts them as “Declined” and “Not Registered” as Response and Registration status in DB view? If that's the case, then it did strike us as weird because sure, Declined RSVPs are Not Registered, but we're also not going to register them - so “Do Not Register” feels like a more appropriate match.

This is what we ended up doing (on an event that we have a little over 4k participants for).

Alex Wong

@Helen Bowen
From others that is replying, I got a better idea of your confusion.

Yes, that's the “difference” in terminology between web/database view, which you can read more about it here:

Helen Bowen

@Rachel Cavalier Thank you, I'm finding it confusing at the moment, so need to find a way to make it work for us. So thats really helpful to know how you've been using it.

Rachel Cavalier

@Helen Bowen
The thing I particularly like about webview is that checking people in at events is really good - works quickly, easy to check in groups on the same booking, search window is great and you can set filters so it's just the people who have said they're coming.

It's just the matching between DB view and webview for response and registration could do with the ability to be customised by us.

Jennifer Kluh

@Rachel Cavalier we are in search of a new way to check our attendees in at our Wine Tasting and Gala. We are trying to get away from using tickets. Thank you for this info and I look forward to checking this out!