"Unexpected values found in emails" when upgrading to 8.0

Hello,

When doing the upgrade from 7.9.4 to 8.0, I had this warning during the healthcheck :

82. Unexpected values found in emails
Invalid status and type for emails: status=read, type=out Learn more...

83. Unexpected values found in emails
Invalid status and type for emails: status=read, type=archived Learn more...

84. Unexpected values found in emails
Invalid status and type for emails: status=read, type=draft Learn more...

The explanation link is broken : http://support.sugarcrm.com/Knowledge_Base/Installation_Upgrade/Troubleshooting_Health_Check_Output/Health_Check_Error_Invalid_Status_and_Type_for_Emails/

I did the update anyway and now all my existing emails have a status of "Archived" instead of Sent/Read/Unread. I sent a new e-mail and it was set to "Archived" instead of Sent.

I saw that in the database, the table "emails" has a new field "state". So it seems that the interface display the state instead of the status of the e-mail because the e-mail has the state "sent" in the database;

How to fix this ?

Parents Reply Children
  • This is more than a silly step beck.  This is very useful when trying to use SugarCRM as a support-system - being able to tell which emails are the new ones relating to a case and not having to look through them all.  Though along with the removal of being able to "send as" a group user, it is becoming painfully obvious that SugarCRM wants nothing to do with the support side of CRM.  Or they have no idea how businesses operate.  Or they want to foster the development of more customizations at he partner level by allowing partners to offer to re-code all of the value back into the email module.  Frustrated.

  • The global Customer Support departments at my company are also very dissatisfied with the two email module changes within the v. 8.0.1upgrade:

    1. The removal of being able to "send as" a group user

    2. The new status of Draft and Archived

    We had to cancel and postpone our go live with 8.0.1 for the first issue and first pay our implementation partner 2 days of programming to create a workaround. We definitely do not want Support emails being sent from personal email accounts.

    The second issue is still und investigation to bring it back to the old status values. Unbelievable, an Email program that is not able to show read and unread. It is the basic idea of emails.

    Also the field object for the text body on the email is not resizable, like other larger fields for descriptions and very small with a second scrollbar at the side. Looking at a larger email text, this is very frustrating. So we had to customize ($$) that one as well.

    Is Sugar still doing any usability tests with customers? Would like to get these issues solved by Sugar asap, or the product manager for the Email module should pay for all the workarounds out of his own pocket.