Open Forum

We are experiencing an issue with our registration form, which is pretty simple, but integrated with Salesforce and is set up to look-up contact information from both cvent and salesforce. 

Step 1/first page of registration form is collecting registration type, email address, and first and last name. here's where the issue happens. The user selects the registration type first, and then the system refreshes the browser and the email address field is null, but now the first & last name are pre-filled with some random information. All fields should be null until the user inputs an email address, which is the first bit of data that can be looked up...

Has anyone else experienced a situation like this? If yes, what was the resolution?

We logged a case with Cvent almost two weeks ago and no resolution yet. 

#Events+

------------------------------
Mary Zampino, CSP, CSMP | Vice President – Content, Research & Analytics | SIG
mzampino@sig.org | LinkedIn: maryzampino
------------------------------

Hi Mary,

Are you using the Cvent Salesforce App's feature that allows you to use Salesforce as an External Data Source? If so, the populating of random name information is definitely odd and I can investigate more. In the meantime, the way the feature is typically used is to collect name and email (identity confirmation fields) on the first page of registration, and alone as their own fields on that page. When they click next, this initiates the look-up in Salesforce based on that email address and if a match is found, can then prepopulate any mapped Salesforce contact/lead fields into the Cvent reg form. In this scenario, you would have reg type automatically assigned if you create rules on the reg path to assign reg type based on fields that will be populated by Salesforce, or you can have reg type as a selectable field on 2nd page of registration.

------------------------------
Ryan Costa
Mas33United States
------------------------------

Thank you for your time and thoughtful response, Ryan. Indeed, we are using SF as external data source, and have deployed as you described. We successfully hosted this configuration for our recent event with no issues.

As of earlier today, Cvent has confirmed the issue, identified a bug and is working with us now.

Again, thank you for taking the time to respond. I appreciate it. Best wishes, M

------------------------------
Mary Zampino, CSP, CSMP | Vice President – Content, Research & Analytics | SIG
mzampino@sig.org | LinkedIn: maryzampino
------------------------------

Original Message:
Sent: 05-20-2024 15:58
From: Ryan Costa
Subject: Registration Issue - pre-filling fields before entering any information

Hi Mary,

Are you using the Cvent Salesforce App's feature that allows you to use Salesforce as an External Data Source? If so, the populating of random name information is definitely odd and I can investigate more. In the meantime, the way the feature is typically used is to collect name and email (identity confirmation fields) on the first page of registration, and alone as their own fields on that page. When they click next, this initiates the look-up in Salesforce based on that email address and if a match is found, can then prepopulate any mapped Salesforce contact/lead fields into the Cvent reg form. In this scenario, you would have reg type automatically assigned if you create rules on the reg path to assign reg type based on fields that will be populated by Salesforce, or you can have reg type as a selectable field on 2nd page of registration.

------------------------------
Ryan Costa
Mas33United States
------------------------------