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!
#848 - To-From-Cc-Bcc fields are being blank
Issue While archiving the emails, the Plugin pulls Subject and Body from Outlook to CRM but fails to pulls To-From-Cc-Bcc.
Expected Behavior The plugin should pull To-From-Cc-Bcc fields too.
Actual Behavior The Plugin pulls Subject and Body fields only
Possible Fix Broken link?
Your Environment Outlook Plugin Version used: 3.0.9 Outlook Client Version used: 2016 MSO (16.0.8730.2046) 32-bit SuiteCRM Version used: 7.9.5 Host (e.g. PC, Server): Hosting Solution One - SuiteCRM:OnDemand Operating System and version (e.g Windows 10): Windows 8.1 https://user-images.githubusercontent.com/34917918/34419773-b722ad14-ebfd-11e7-819c-2845f6240e13.png
- Most Recent Love from Users
rimacoca- Ricardo Cairello
- marcusvsgimenes
- Ricardo Cairello
- thermoprintix
- clientes
6 years ago
Hi jay1,
Is it possible if we could ask you to send your Outlook DEBUG logs (logs set at DEBUG level) while replicating the issue to our support email address outlook[at]salesagility[dot]com referencing this Ticket #848. If you could also include what PHP version you are running off of, that would be much appreciated and we'll investigate.
6 years ago
Dear SuiteCRM Outlook Plugin Team,
Request you to confirm to be in receipt of the requested files and provide us an update on this issue at earliest.
Thanks!
6 years ago
Hi jay1,
We have received your PHP version but not the outlook plugin logs. You can find these inside outlook -> SuiteCRM tab -> settings -> information. If you could again send this to outlook[at]salesagility[dot]com referencing this Ticket #848 we will be able to investigate further.
Thanks.
6 years ago
Hi jay1,
We've received your logs and will get back to you as soon as possible with an update. Thanks.
6 years ago
Hi jay1,
Just as a quick update. We've managed to confirm this issue and a fix will be included in the next release.
Thanks.
6 years ago
Thank you for an update.
When can we expect the next release?
6 years ago
Thank you for an update.
When can we expect the next release?
6 years ago
Hi jay1,
I can't provide an exact ETA but we are looking to release the next version v3.0.10 as soon as possible. Thanks.
6 years ago
Thanks for your reply. Can we expect the next version within next couple of months or more?
6 years ago
Hi jay1,
I would expect v3.0.10 to be released sometime in the next few weeks.
5 years ago
This has been resolved in 3.0.18