Official SuiteCRM Outlook Plugin v4 has arrived - Compatible with the Outlook Web App or Outlook 2016+ connected to Office365 or Exchange Server 2016. A complete rebuild developed and maintained by SuiteCRM developers, the addon retains previous functionality while massively improves performance, reliability and stability!
#3716 - Issue with user list on licensing screen
Hi
There is a bug with the Outlook Users panel that appears on: /index.php?module=Administration&action=OutlookAddinConfig
If you try and sort the list by Name or Email, you get a DB error - e.g.:
Error retrieving User list: Query Failed: (SELECT users.* FROM users WHERE sa_outlook_is_licensed != 0 AND deleted = 0) ORDER BY full_name desc LIMIT 0,10: MySQL error 1054: Unknown column 'full_name' in 'order clause'
(This can be worked around by sorting by User Name)
Cheers
3 years ago
I started having this issue today also, which I managed to fix by going into our SuiteCRM database -> Users table, then creating a new column 'full_name' with no data inside. This seems to fix the error (Though obviously is not an ideal fix as it makes the 'order by' part quite useless).
It could be worth it to create the full_name column as a combination of first_name + last_name, but I didn't as we don't necessarily need it to be ordered, for our purposes. (As we only have 1-2 right now for testing purposes)
I didn't know that sorting by User Name was a fix - will keep that in mind, although I don't think it will be needed from our end any more
3 years ago
Hi info121
You'd also need to create an email1 column on the table if you wanted to avoid the error entirely - as sorting by email has the same issue. But I wouldn't necessarily recommend making table changes as there may be code that relies on column position or there may be code in the future that relies on these columns not actually being present etc. etc. But it def. works as a quick fix - hopefully the Suite guys should pick this up soon...
Cheers
3 years ago
Hi there,
Thanks for the report! I'll take a look at this issue and raise it with the team!