Breaking news from around the world
Get the Bing + MSN extension
The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Today’s #TipTuesday is a post about Office 365 and Dynamics GP and is specific to email functionality such as emailing Purchase Orders, EFT Remittances and Sales Documents. Rest assured that most other functionality other than email seems straight-forward and works no matter what (like exporting from Smartlist). (At least that’s my experience although there may be exceptions I am unware of!)
The email server type settings are in the System Preferences window, on the Administration pane and there is a choice of MAPI or Exchange. The short version of compatability is this:
My former employer is in the process of switching from Office 2016 to Office 365. Some workstations are updated, some are not. They were set up with MAPI settings but we changed this to Exchange in order to be compatible with all workstations pre- or post-update.
Here are some things that may be helpful if your organization is undergoing the same kind of change.
The first thing you want to do, especially if you have a mix of Office installs, is ensure that the setting will work for everyone. In my example, this meant changing the System Preferences setting to Exchange.
Here is what the error is if you don’t, and have Office 365. I assume the same error would occur if you use 64-bit Office but I can’t confirm based on personal experience.
The error message is “Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client”. Of course, when I got the error in testing, Outlook is installed but on my workstation I had already been updated to Office 365.
The second/subsequent error says: “Connection to the MAPI server not available. Unable to send e-mail or select addresses”.
The System Preferences were set to MAPI, as shown below. We changed this to Exchange for compatability.
With the change, we were compatible with both versions of Office as well as 32 and 64-bit installs so that’s the good news. The not so good news perhaps is the users now have a little more “clunky” UX to work through. With Exchange, they now have to provide their email and password. This persists to a certain extent:
The other thing, something I don’t have a screenshot for, is with MAPI, if you wanted to email a report, the pop-up window was an Outlook mail window. With the Exchange server type setting, it’s a horribly plain looking generic send mail window that users might take a bit of getting used to. Little things like no auto-complete on email addresses are off-putting at times!
There may or may not be issues you would encounter with this change that others have asked about on various forums. Instead of copying those things verbatim, I will list them here in no particular order:
This post by the Microsoft Dynamics GP Support team may help with some troubleshooting: https://community.dynamics.com/gp/b/dynamicsgp/archive/2013/08/27/e-mail-error-in-microsoft-dynamics-gp-2013
1. Some users find they need to “Show Advanced” to also input a Login ID (i.e. Network alias). We didn’t experience this in our environment and we were running GP 2016, for reference. This is likely driven by either version of GP or some configuration within Exchange or Office 365 itself.
2. Some users are unable to authenticate at all and require a registry update. This thread alludes to an insert being required into SY04920.
Those seem to be the most common things I’ve seen or heard with respect to Office 365 and email functionality in Dynamics GP.
Business Applications communities