Contact Emails being stored in user's email field.

[paulgmcdonald]

When a user on my SUGARCRM instance enters a new contact, the email that is entered for the contact is also stored as the user's email address. We are using Version 5.0.0g (Build 3391).

Can anyone help with this?

[DragonflyMaster]

When a user on my SUGARCRM instance enters a new contact, the email that is entered for the contact is also stored as the user's email address. We are using Version 5.0.0g (Build 3391).

Can anyone help with this?

This is quite peculiar...
Would you explain where exactly do you see this?
I can't see any user's email field in Contacts.

[paulgmcdonald]

I have just upgraded to the latest release(5.1.0 build 4732) hoping that the issue goes away, but it does not.

Here are the steps of what I am seeing.
Click CONTACTS
Click Create Contact
Enter firstname, lastname, email address as primary
Click SAVE
Then goto ADMIN -->User Management
Select the user that the contact was assigned to
Now the user's primary email address has been changed to the email that was put in for the contact above.

[DragonflyMaster]

I have just upgraded to the latest release(5.1.0 build 4732) hoping that the issue goes away, but it does not.

Here are the steps of what I am seeing.
Click CONTACTS
Click Create Contact
Enter firstname, lastname, email address as primary
Click SAVE
Then goto ADMIN -->User Management
Select the user that the contact was assigned to
Now the user's primary email address has been changed to the email that was put in for the contact above.

I tried to recreate the same behaviour on a test 5.0.0g install, but everything goes fine, my user has the his own email address even after inserting the contact.
Maybe there's a conflict on the two fields' names in the files or maybe someone messed with the database .
Upgrading to 5.1 might have kept a hidden "bug"...

[paulgmcdonald]

hmm .... any idea where I would go from here?

[DragonflyMaster]

If you've already tried the repair functions unsuccessfully, you could try to get rid of the whole cache, renaming the cache folder and reloading Sugar.
Renaming the cache makes Sugar build a new one from scratch without any risk for the old one.