TOPIC: Community Builder Sync - Confirm Email field

Hi,

Hopefully a quick question. Been working on the 2.7.2 installation tonight and have gotten CB profiles to sync with DT Register events during signup*.

One field that will not pre-populate via the sync is "Confirm Email". It's a required field on the DT Register Event registration. I'd like to either have it force pre-population with the user profile's email address (as is done in the field above it -- "Email") or turn off "Confirm Email" as a required field for registration. I've watched several of the YouTube videos, but haven't seen anything on it.

Is there a quick fix for this one? Once this is out of the way, my users won't have to type anything in when registering for an event. This is highly valuable for my non-profit.

Cheers!

-soccerbum
* - As a side note (and maybe something to add to the next patch), the CB profile integration lists 'firstname' and 'lastname' fields, but I originally set up CB to use a single field for both the first and last name. After seeing that DTRegister doesn't have an option to map a 'NAME' field (only 'firstname'/'lastname'), I made a config change in CB so that things would work with with DT, but that now means I have 650+ members who will need to update/change their profiles. Ouch! It would be SO nice if I could just map the CB single name field to a single name field in DT Register (even if we'd use a shortcut and just map CB's 'NAME' field to DT Register's 'firstname' equivalent)...

Hey, the confirm email field will purposely not auto-populate. If your data is always auto-populating, then just disable the confirmation requirement. Any email field in DT Register has the option to enable/disable the confirmation field. In the field manager, open the email field and you will find this parameter.

You are right... DT Register has always been intended to use with CB set to First and Last Name. At this time, you can't sync just the full name as the two name fields in DT Register are presently required. Thanks.

Drilling down to the email field and disabling confirmation did the trick thanks!

As an aside, if it isn't in the documentation for DTRegister already, can you add a blurb in the CB integration bit mentioning DT only integrates properly when CB is set to distinct first and last name fields, rather than using a single name field? Hopefully it'll save someone else the pain I'll be going through in the next week or so.

Thanks for the help!

-soccerbum