I guess all is in the question
I actually have this problem.
I have an app that is basically B2B2C. My app lets companies set up sales in my site and customers can view the sales.
I can have a business register a new user that works for their company. And I’ll use “create an account for someone else” and it works great.
But, yeah, they may already exist as a customer in my site. So I just coded a check to make sure that the email address isn’t already in my user table.
If it is, that means that user already exists as a customer, and I pop up a message that the app already has that person as a registered user. I display the email and the name and ask them to confirm that this is the user they want to add to their company.
If so, then I update the user as I need and send that user an email that they are now a part of the company.
I don’t know if this exactly addresses your problem. But hopefully it helps.
I have no problem per se. I want clarification of the acton behaviour:
- Are the fields still updated if the user already exists or not at all?
Apparently the answer is 42…
Answer is yes