It’s important to note that Dynamics GP 2016 is out of mainstream support in July 2021 so that version will not receive any further year-end updates for regulatory changes, so you will need to organise an upgrade to the latest version next year.
This post is on the Support for Multi-Factor Authentication (MFA) System enhancement.
The Fall 2020 release adds the ability to use Multi-Factor Authentication for e-mail functionality in Dynamics GP; this functionality uses an App Registration in Azure Active Directory along with Microsoft 365 to provide a second form of authentication.
The process of configuring this App Registration is covered in the What’s New section for the Fall 2020 release on the Dynamics GP Docs site.
The configuration in Microsoft Dynamics GP is done via Company E-mail Setup:
The plugin I am going to cover in this post, is a brand new one written for ClassicPress; Widget Announcements.
Announce holidays, events, achievements and notable historical figures in a widget.
Announcements can be made:
- One off
- Good Friday
- Easter Sunday
- Easter Monday
- Monthly on the nth day (e.g. 2nd Wednesday of every month)
- Annually on the nth day of the month (e.g. 4th Thursday of November every year)
Announcements are created as a custom post type and can have details, an image, additional text after the image and can be assigned to multiple categories. A widget can be deployed to a sidebar or other widget area and include the announcements from a category.
The plugin can be downloaded via my Development site.
When using the Web Services for Microsoft Dynamics GP with external access for Workflow approvals, it is important that the webs services be secured to minimise possible attack vectors. Everything covered in this series is required to install and configure the web services for internal use only
I covered the process for enable a secure connection for the web services a year or so ago which include a few extra steps:
|Enabling Secure Connection for Web Services|
|Before You Begin|
|Update Certificate Binding|
|Update Legacy Endpoint|
|Update Native Endpoint|
|Update GP Workflow Service|
|Final Service Configuration|
|Configure Workflow Setup|
The final step with the Web Services, now that they have been configured, is to verify that they are working correctly.
There are three checks which I recommend when verifying the web services:
- Is the service running?
- Have the security objects been deployed?
- Are the endpoints working?
To check that the service account is running, open the Services applet from Computer Management (or hit Win+R and typeServices.msc) and make sure the Microsoft Dynamics GP Service Host is set to a Startup Type of Automatic and that the service is Running.
With the Web Services installed, the next step is to configure them for use. If you marked the checkbox on the final step of the installation the Configuration Wizard will start automatically otherwise it can be started from the Windows Start menu. Click NExt to start the configuration:
With the Web Services for Microsoft Dynamics GP prerequisites ready, we can now install the web services. Launch the setup utility and, under the Additional Products heading, select Web Services Runtime:
The next few posts are going to cover the installation of the Web Services for Microsoft Dynamics GP.
Before we start the installation itself, there are some prerequisites to make sure are sorted out. The majority of them will be installed by the setup utility, but there are others to consider.
Firstly, the Web Services should not be installed on either the SQL Server or an end-user accessible machine. If you’re going to make the Web Services externally accessible, they should be installed on a web server or similar machine.
Secondly, a Domain account is required for the Web Services service to run under. During the installation, this service should have local administrator permissions.
Thirdly, all companies which will have the Web Services deployed, needs to have a Functional Currency defined (this is needed even if you are not using Multicurrency; in this case, you will need to configure it for use anyway. When you do so, if you have a lot of hsitorical transactions, plan ahead and allow a lot of time to run Check Links).
Once Integration Manager has been installed, we can run it for the first time. When launching it for the first time, make sure you do so using right click and Run as Administrator to make sure it has the elevated permissions necessary to create the required registry changes.
Click the Register Now button: