It is my understanding that if a customer has an email address in the database, but it is not associated with a web login (in T_CUST_LOGIN), then that customer will be unable to use that email address to register for a new web login (due to the preexisting address) and will also be unable to recover the account online (due to the lack of an actual login to recover).
Assuming that is true, would anyone recommend a good workaround for this situation? The best I can come up with is to create a procedure that runs periodically and creates web logins for email addresses that haven't already been associated with a login. This seems pretty clunky, though. Thoughts?
It is my understanding that if a customer has an email address in the database, but it is not associated with a web login (in T_CUST_LOGIN), then that customer will be unable to use that email address to register for a new web login (due to the preexisting address) and will also be unable to recover the account online (due to the lack of an actual login to recover). Assuming that is true, would anyone recommend a good workaround for this situation? The best I can come up with is to create a procedure that runs periodically and creates web logins for email addresses that haven't already been associated with a login. This seems pretty clunky, though. Thoughts? You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!