Title shows in First Name and First Name shows in Middle Name field - after processing event registrations

After processing event registrations in the plugin, you notice the constituent's Title shows in the First Name Field and the First Name shows in the Middle Name Field. You want to know why the fields are not in their proper areas. 

Fill out an event registration form, with a shortened first name for the registrant information, the title field, and using a full name for the billing info. For example, Mr. Jon Smith is the guest, and Jonathon Smith is the card holder. When in the plugin, we reject the Title and long First Name of Jonathon. After processing the transaction, and opening up the participant information in the batch, we see that the Title has been added to the First Name Field and the First Name has been transferred to the Middle Name Field.

When you register for an event on NetCommunity with guest information and process the transaction on the NetCommunity plugin on RE then when you view the guest record the mapping of the title, first name and surname are incorrect. The mapping incorrectly displays the first name as the title, middle name as the first name however the surname is fine.
Typically, this is the result of a corrupt event registration form. Often, the event registration form may have been copied many times. To resolve, create a brand new event registration form part. Do not copy the event registration form.

If the behavior is persistent after creating a new event form, check the version of NetCommunity and confirm all components are on a matching version, preferably the latest version.

Steps to Duplicate

One known steps to duplicate for event transactions:
  1. Navigate to the event registration page
  2. Enter quantity 1 (or more) and click Continue
  3. For the Registrant Information, enter Mr. Jon Smith, and other guests you may have chosen, depending on the quantity
  4. Click Continue
  5. Fill out Payment Information, specifying a different name, for example Jonathon Smith, and click Submit
  6. Open the plugin in RE
  7. Click the Event Registration link
  8. Select the event registration to process
    1. If you created a new constituent, click Create New and Edit
    2. If you are linking to an existing constituent, click Find Constituent and link
  9. When the option to choose which profile updates to keep, reject Title and First Name
  10. Click Save & Close
  11. Click Yes, you want to reject remaining updates
  12. Click Process Transaction
  13. When the batch is up, select your row in the batch
  14. Select Gift>Links>Event>Registration Fees
  15. Select a gust and click Open participant
  16. Click the ellipses next to the Registrant
  17. Note: First Name shows the Title from step 3 and Middle Name shows the Name from Step 3.
After you commit the batch,you’ll see the same information when opening the event record.

Another scenario of steps to duplicate:
On form:
  1. Navigate to your event page
  2. Enter a quantity of 2 for the Individual registration and click Continue
  3. Enter required fields, including the Title Field.
    • Note: Ensure the Main Registrant and Guest registrant have different names
    • Note: Ensure that you are using existing Constituent information from RE for the paying registrant. The issue will not occur if you create a new constituent.
  4. Click Submit

In RE:
  1. Open Raiser's Edge
  2. Open the NetCommunity plugin
  3. Click the Event Registrations Link
  4. Link the constituent in the plugin or create new
  5. Click process transaction
  6. Click Ok on the prompt for no fees
  7. Open Records>Events>Open the Event test for duplicating title - first name mapping
  8. Select the Participants tab
  9. Double click to open your Participant
  10. Click the guests button
  11. Double click to open the guests.
    • Note: guest has Title in First name and First Name in Middle Name 

For a 2 x 2 ticket (example, Couple ticket for 2 couples) the result is:
Ticket 1 a: Expected
Ticket 1 b: Unexpected
Ticket 2a: Unexpected
Ticket 2b: Expected

For a 2 x 1 ticket (example, registration unit has 1, but 2 tickets are purchased)
Ticket 1a: expected
Ticket 1b: unexpected (guest record)

Was this article helpful?

Thanks for your feedback! Did this solve your issue?

Comments (optional):

Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):

Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.