Mapping Event Module data to webview Event Tile

shani traum

We have had the Event module in RE7 for over 15 years. Thus far, the information there has not come over fully to NXT and some of the coding that has isn't playing nicely with NXT. I have heard nothing (not been able to get any information) about how data from the module will be coming over to NXT, if there will be the opportunity to fully map data, etc. Does anyone have any intel? There was been alot of talk about the new Event Registration capability in NXT, but nothing about the existing data in the event module.

Daisy Alarcon

Hi Shani, thanks for flagging this. I don't want to guess at what specifically isn't coming over, since "the Events module" covers a lot of ground (fees, custom fields, registration forms, participant options, and so much more), and it'd help to know what you're actually hitting.

What's true generally: Events in database view and web view were built differently, and even though they are synced to display in both places, they are managed and surface information differently. Could you share an example of what you are not seeing transfer? That'll help us point you to either what the new workflow is in RENXT, if there needs to be a fix, or flag it as a real gap.

Thanks!

shani traum

Thank you Daisy!

Event Fees: in DBV events module, this includes a place to put a description of what’s included in the fee.  This is needed to both track for future record keeping and also this info pulls into Luminate when creating an event.  Also, it is used to determine actual receipt amounts based on donor usage.

Category in dbv is Dinner, Sporting Event, Class, Other and Group (for us) is Development, Leadership.

As example:
A dbv event with Category = Dinner and Group = Development.
In webview, the “Category” shown is Development and the “Group” shown is blank.  So, the mapping is messed up.

On the Participant records there are also fields that are missing or not mapping fully.
»Response in dbv does not come over to webview (we have an extensive list of option in use for this)
»Registration in dbv maps to RSVP Response in webview,
»Registration = Registered maps as Attending in webview, but that's not how we've used it (for us, it just means they responded one way or another, and this means all stats in webview are incorrect)
»Status doesn't come over to webview

I hope this all makes sense! And thanks again for taking a look at this.

Shani

Daisy Alarcon

Hi @shani traum,

Quick frame before the specifics: RENXT Events and the database view Event module aren't the meant to be the same. They share the same underlying database, but the web view experience and workflows were built differently on purpose. That's the lens for everything below.

Category
Database view actually has two separate fields here, Category and Type. Web view only has a single Category field, and it maps to the database view's Type field, not database view's Category field. Documentation: https://webfiles-sc1.blackbaud.com/files/support/helpfiles/rex/content/events-settings.html

Here's the fix: if you would like to categorize your events in web view moving forward as similar to the categories in database view, then you need to add matching entries under Events, Events settings, Event category.

Group
This one's more straightforward. Group lives directly on the event record in web view, under Edit, Event details, and comes from a separate table in Settings, Tables. So if Group is showing blank, that's the place to check and set it: https://webfiles-sc1.blackbaud.com/files/support/helpfiles/rex/content/events-event-details.html

If you are still seeing inconsistencies, then please file a support case for our team to help you investigate it further: https://support.blackbaud.com/support-home

Fee Description
You're right, the comment/description text on the price unit in database view doesn't carry over to the Fee record in web view. That's a real gap, not something I can offer a workaround for. Please submit it to the Ideas Bank with the receipting and Luminate context you gave me. That's genuinely the best path to get votes and product attention on it.

Response field
Response was one of three database view fields we looked at when we were building out RENXT Events back in 2020. Along with Status and Registration, it's a way customers tracked invitation replies, but since Response and Status are custom, user-defined tables that vary by org, neither was brought into web view as its own field. Instead, RSVP status was built by relabeling Registration with a standard set of values. Background: Capture RSVPs in RENXT Events

Registration to RSVP status, and why Registered = Attending
This is working as designed - let me explain. We renamed the existing Registration field to RSVP status in web view and expanded "Registered" and "Not registered" into a fuller set of options. Attending is just the new label for whatever was already saved as Registered. Interested, Waitlisted, Declined, and Canceled all map back to Not registered (and per a later update, Declined and Canceled now map back to Do not register) in database view.
Background: Capture RSVPs in RENXT Events
Current documentation: https://webfiles-sc1.blackbaud.com/files/support/helpfiles/rex/content/events-rsvp-status.html

One nuance: a database view registrant left at the default Not registered shows as No response in web view, not Declined, so that default isn't adding noise to your Declined counts specifically.

Status field (the one you used to mark who'd paid)
Status was the second field that original change addressed, same reasoning: custom to each org. In your case, the paid-tracking Status did has been replaced, not dropped: the participant list in web view has a Registration fees column that automatically calculates total fees and remaining balance from the linked Fees and Payments, so there's nothing left to manually update.
Documentation: https://webfiles-sc1.blackbaud.com/files/support/helpfiles/rex/content/events-participant-reg-fees.html

Thanks again for laying all this out so clearly. We have a plethora of resources from product docs, to trainings, to asking our support team or continuing to ask your fellow RENXT community here if you have any further questions as you continue to dive into RENXT Events.

All the best,
Daisy

shani traum

So, I'm confused and if there's some other mechanism I should use to discuss this/get answers, please let me know.

"

Response field
Response was one of three database view fields we looked at when we were
building out RENXT Events back in 2020. Along with Status and
Registration, it's a way customers tracked invitation replies, but since
Response and Status are custom, user-defined tables that vary by org,
neither was brought into web view as its own field. Instead, RSVP status
was built by relabeling Registration with a standard set of values.

So…there's a field that customers are using to get detailed info, they weren't brought over? It's a table driven field, so why couldn't it come over? Other table driven fields were carried over to NXT - why not this? And what happens to that historical info once the transition is complete? Also, is there a way to build out the current options for response as they do not capture all options, for us?

Status field (the one you used to mark who'd paid)
Status was the second field that original change addressed, same
reasoning: custom to each org. In your case, the paid-tracking Status
did has been replaced, not dropped: the participant list in web view has
a Registration fees column that automatically calculates total fees and
remaining balance from the linked Fees and Payments, so there's nothing
left to manually update.

Same question as to why this couldn't be brought over as it's table driven as many other fields are. Status doesn't just track if they've paid or not, it tracks, for us, if they were comped their ticket - which fees paid doesn't help with.

And again, how will historical info come over or is that all lost?