At BBCON, this was the audience choice for the next Online Data Review feature in the Unified View Super Session, so I hope it gets added soon! I'll echo other comments in saying this is preventing us from moving to RENXT events; the lack of data review creates too many duplicate records.

Is it possible to add a review step, let us to make the final decision. it would be great if we can review the new registrants before the final match/create new records. It is also helpful for us to find new emails/phone numbers from new registrants.

Why did blackbaud stop allowing manual approval of event participants, especially new constituents? How is matching a name with an email accurate and then creating a new record if the email does not match, especially when emails change constantly. This is the lowest level of authentication. Many believe this is Blackbaud's way to increase customer record count so they can charge more money on top of increasing everyone's fees every year and not responding to the needs of customers. I know many large nonprofits leaving blackbaud because of these sneaky practices that they think will go unnoticed. It is fraud.

Yes, I loudly echo this request. We are wanting to leverage the NXT events forms for direct online registrations, but they create a mess of cleanup for our team due the combination of overly simple constituent matching and the lack of a review step before creating potentially duplicate constituents. Please prioritize fixing this issue.

This is the #1 reason we have not switched over from OLX Events to start using the NXT event registration forms.

This is desperately needed to make the NXT online event registration useable.

This should work for people who are guests of another registrant as well. We have a lot of spouses that end up as just a participant on the event when we have them in the database.

Please implement a review process or set up controls in RE like in Online Express, where you can approve / commit the creation of a new constituent record for a registrant not matched to a pre-existent constituent record. Not all registrants need to be in the database as constituents. With Latin names, or names that have accented letters, names misspelled during registration, etc, it will just create lots of duplicates.

I would upvote this 100 times if I could. I waste SO MUCH TIME on deduping records because new records get generated through event registrations. We have to dedupe EVERYTIME we want to send any kind of communication (mailing or email). And we lose the information about what the preferred address or email was when the new record is created. so so annoying!

This is so needed! Please also see idea 7111 and 7053.

This is still an issue, and it makes using the Events option impossible.

Please fix this flaw. We shouldn't have to choose between database integrity and cleanliness and using the integrated events solution.

I can't believe this still doesn't exist.

A corollary to this would be to allow all changes to a record that would be made a result of event registration to be reviewed before they are committed to the record. Since we implemented event registration forms, I am constantly finding that our correct, Address Accelerator'd addresses are being overwritten with whatever random combination the constituents used. This is most often displaying in a space after the city name, so that their addresses are now showing up as "City Name , State."

Please, Blackbaud. The amount of time we're losing having to clean up duplicates and bad addresses does not make up for the convenience of event registration forms.

I'm about to disable event registrations in NXT and send our staff back to using BBNC if this doesn't get fixed. We had a duplicate created for a significant VIP with no contact information whatsoever. We at least need the option to manually review registrations before changes are made to records.

Hello,

We are opening up some discovery sessions around the topic of visibility and review of records created from NXT webview online registration form submissions when no match is found.

We are looking to speak to your event coordinators and whomever manages the duplicates that can be created from the online registration form.

In order to be eligible for this discovery, you must have used the webview registration form for at least one event that had real (not just test) registrations and be familiar with the webview participant management functions.

We are looking forward to showing you some ideas we are considering and how they may fit into your event and data management processes.

This is a hot topic and discovery spots are limited! If you are interested in talking to us, please email me at samantha.mcguin@blackbaud.com and I will email you back with some available call times if openings are still available. These will be setup on a first come first serve basis.

Thanks,

Samantha McGuin
Principal Product Manager
Blackbaud
Samantha.mcguin@blackbaud.com

YES! Please! Actually, please allow us to review all matches to make sure they are correct—just like we do using BBNC registration forms and the BBNC plug-in for RE. The fact that NXT event reg forms automatically create constituents and automatically update records with no human intervention is a deal-breaker for our Operations team, the guardians of our data. Clearly, BBNC is an end-of-life product and we're eager to move over to a product that is getting new features, but can't yet.

Yes, please. This is a feature in Online Express that is missing from NXT web view forms.

Ditto previous reviewer. We have duplicates created for almost all registrants. Also - when someone registers for a virtual event and leaves the address field blank, the blank address becomes their preferred address.

Also, the ability to add non-constituent registrations. We don't want send mail to a 5 year old just because they participated in a WALK or another event.

Yes this is very needed if NXT donation forms are to be taken seriously.  6 out of the 8 new constituents NXT created from our test run with an NXT donation form were already constituents or the spouse of a constituent.  In a couple of the cases their name and address exactly match the primary constituent in RE, so I have no idea why it did not catch them.