In my DR setup I have the DNN Core Integration set to:

Username Field = Email Address

Email Field = Email Address

About 50% of all registrations have no Email Address in the DNN Users table and after speaking to too many of them, they've also never received a welcome email that's part of the completion event.

Since we are using Dyna Login and users are instructed to enter their email address for the username, people without a email address in the users table cannot login. This is compounded by the user trying Send Password and being told the username doesn't exist. Some attempt to register but get blocked because that email address is already used.

Most important issue: How can I determine why some  email addresses are not sync'd with the Username and prevent this in the future?

I can fix the users who currently are caught in limbo by manually updating the Users table with a SQL script, but even after doing that I have new users who are out of sync.

Help please.

DR version = 04.00.30

DL version = 03.10.20

DNN version = 04.09.00

 

Ralph

PS. As a work around I've added a completion event to sync email address with Username and made that the 1st event. I'm still getting registrations with no email = username.

 

 

 

HI, I don't know if this will fix the issue but generally speaking, it's not proper to map in the DNN Core Integration area two fields (username, email) to the same DNN core profile. If you want the username = email, I would recommend to do the following:

1) still have a "username" field on your form, but make it a hidden field or read-only textbox field
2) use client side event on the email field to set the username = email field like this:

$(username) = $(email)

This way, there is a username and email core profile field but both are in actuality, identical. -- David