Mistyped Contact Information

What can I do if I’ve mistyped a contact’s email address?

Note: If this is NOT an e-commerce related contact these steps do not apply. Simply adjust the email address in HUB and save the contact record.

IF the user is initially setup through an outside customer registration (dwdiesel.com/register)

The scenario looks like this:

1. An outside customer registers for the website.

   1. ID = GUID ABC123

   2. Email = [e-mail]

2. The customer is determined to be a valid e-commerce user.

3. D&W Staff creates the contact in HUB, but mistakenly mistypes the email address.

   1. ID = 1000025227 (Universe generated ID)

   2. Email = [e-mail]

   3. Customer association = 129636

The middle-ware processes this contact record as if it is a NEW e-commerce user. So the user, 1000025227 with email [e-mail] is created under buyer 129636 in ordercloud (and therefore admin.dwdiesel.com).

                4. D&W staff recognizes the mistake and updates the contact record in HUB:

                          a. ID = 1000025227

                          b. Email = [e-mail]

The middle-ware processes this change in HUB and matches the email address [e-mail] to the user in the Registration queue with ID = GUID ABC123 and updates that record’s ID to match HUB = 1000025227.

The middle-ware now tries to perform the MOVE function on the user to move them from the registration page (anonymous buyer) to the properly associated buyer 129636. However that MOVE fails because there is already a user with ID = 1000025227 associated with buyer 129636.

Correct this discrepancies by:

1. Within admin.dwdiesel.com, delete the user 1000025227 that exists under buyer 129636 (this should be the user with and incorrect email address).

2. Within hub.dwdiesel.com edit the contact 1000025227 by removing the associated customer 129636

3. Within hub.dwdiesel.com edit the contact 1000025227 by adding the customer 129636

The middle-ware processes this change, matching the ID 1000025227 to the user on the registration page and this time successfully performing the MOVE function to associate the user to the buyer 129636.

IF the user is initially setup through a FSR creation from within an existing buyer (admin.dwdiesel.com)

The scenario looks like this:

1. D&W Staff creates the user within admin.dwdiesel.com, but mistakenly mistypes the email address.

   1. ID = GUID ABC123

   2. Email = [e-mail]

   3. Customer association = 129636 (automatically associated because the user is created within the context of a buyer)

2. This user is created automatically in Universe and assigned a Universe ID

   1. ID = 1000014172 (Universe generated ID)

   2. Email = [e-mail]

   3. Customer association = 129636

The creation in Universe triggers the middle-ware to update the record in ordercloud with the Universe generated ID 1000014172, replacing the GUID ABC123.

       3. D&W staff with HUB access can simply edit the contact to fix the email address and save                                 the record.

                 1. Email = [e-mail]

The middle-ware processes this change and updates the user in ordercloud by matching the ID 1000014172 that exists under buyer 129636.

Additional Questions? Please submit a request below or e-mail [e-mail] and we'd be happy to help.