Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit RENXT-I-2743 Ability to review event participants who are not auto-matched.

Prevent NXT from creating or changing records for event registrants Merged

If a constituent fills out an event registration on NXT and there is any difference in the name (such as a nickname) or address/email, NXT automatically creates a new record without a Constituent Code. This creates a duplicate record every time. We have to run a query on a regular basis to look for these duplicates and merge them with the constituent's original record. Also, if they leave the address lines blank on the registration form, NXT changes their Preferred Address, leaving it blank as well. There has to be some way for us to link to records and approve any changes before they are made, just like in BBNC.

Admin note: User can configure a constituent code on the event registration form Get started screen that will write the constituent code to new records created. Also, we have added additional usability around optional addresses and made a fix that prevents country only addresses to be written.

  • Carol Sanders
  • Sep 17 2021
  • Reviewed: Voting Open
Online Registration
  • Admin
    Samantha McGuin commented
    October 07, 2021 17:22

    Hello,

    Thanks for your idea! I wanted to respond to a few parts within it.

    There is a configuration option when you setup your registration form where you can enter a constituent code. This will write the constituent code for NEW records that are created when a match to an existing record is not found. This should help you find new records that are created from your registration form.

    I did confirm that when a registrant selects the country on an optional address entry and doesn't enter in any other fields, a blank or partial address record is written. We believe this was likely a usability issue, as the optional label didn't show up until the address lines fields after the user would have already entered in their country. We've fixed this in two ways:
    1) we no longer are writing an address when it contains only country
    2) we've added more visibility to optional addresses to indicate that all address fields are optional.

    This leaves your idea around a request to be able to review the data before it comes in. We do have some plans in early 2022 to give you more visibility into new records that were created and an easier workflow, from within events or gift batch, to see those new records and review possible duplicates without having to go to the merge duplicates screen directly. As such, I will merge this idea into another one that exists around a review process.

    Thanks again for your feedback!

    Samantha McGuin
    Principal Product Manager

    Attachments Open full size

Related ideas