Microsoft Dynamics GP Roadmap to 2028 and Beyond

Microsoft Dynamics GPTerry Heley on the Dynamics GP Support and Services Blog posted an article on Friday on the exciting future of Microsoft Dynamics GP and giving a Lifecycle Update. As part of the article she inked to the published Lifecycle (Roadmap) for Microsoft Dynamics GP which extends to 2028 and beyond for Microsoft Dynamics GP.

The published roadmap also shows the end of mainstream and extended support for versions older versions of the product which predate the Modern Lifecycle:

Microsoft Dynamics GP Roadmap through to 2028

In brief:

  • 2013 and 2013 R2 are out of mainstream support and in extended support until 11/4/2023.
  • 2015 and 2015 R2 are out of mainstream support and in extended support until 14/4/2025.
  • 2016 and 2016 R2 are out of mainstream support on 13/7/2021 and in extended support until 7/4/2026.
  • 2018 and 2018 R2 in mainstream support until 10/1/2023 and in extended support until 7/4/2026.

Microsoft Dynamics GP is now under the Modern Lifecycle and has the same commitment from Microsoft as Dynamics 365. The Modern Lifecycle means there should be more frequent updates to Microsoft Dynamics GP with at least three updates a year in January, June/July and October.

Microsoft will continue to keep adding new features and improving it based on direct feedback from users. The best way to make sure you continue to benefit from the improvements is to keep up-to-date on upgrades and use the latest version of Microsoft Dynamics GP.

The key takeaway from the published Lifecycle is that Microsoft Dynamics GP is not going anywhere and development will continue under the Modern Lifecycle policy with multiple releases each year.

Microsoft Dynamics GP Fall 2020 Release fixes recent Word template issue

Microsoft Dynamics GPA recent update to Microsoft Office broke the Word templates produced from Dynamics GP for both workflow notification/action emails and emailing of Word template documents (such as remittances, orders, invoices and so on). A few days after Microsoft shared details of the problem, they said a fix would be forthcoming and it is included in the 2020 Release.

This does mean that if you are on any version of Dynamics GP 2018 or on the 2019 Release, you will need to apply the 2020 Release update; a fix for Dynamics GP 2016 will also be released, but the method of approach is still being determined.

Install Dynamics GP Web Services from the command line

Microsoft Dynamics GPI was giving a colleague a hand with a Microsoft Dynamics GP 2018 R2 upgrade recently (the client didn’t want to upgrade to the very latest version) and we encountered a problem with the installation of the Web Services:

Clr method invocation failed

Setup.exe .NET Framework Error

Clr method invocation failed

Continue reading “Install Dynamics GP Web Services from the command line”

SSRS requires that you use local SQL Server relational databases… error

Microsoft SQL ServerMicrosoft Dynamics GP ships with a set of default reports which can be deployed into SQL Server Reporting Services; before doing the deploy, there is a setting in the SSRS web.config file which needs to be changed to avoid a maximum request length error.

Recently, when performing an upgrade of a clients system to Microsoft Dynamics GP 23018 R2, the deployment of the reports went fine, but we encountered a problem while testing the deployed reports:

SSRS reports error message

The client had a licenced version of SQL Server 2018 Web Edition which worked in all other respects; the SSRS service was running locally on the SQL Server which was hosting the databases for both SSRS and Microsoft Dynamics GP itself.

This wasn’t something I’ve encountered before, but, fortunately, a colleague had. The problem is not with the Web Edition itself, but rather with the data connection deployed by Microsoft Dynamics GP for the reports. When the data connections are deployed, there is a space created preceding the Data Source name:

Connection settings in SSRS Manager

The fix is to go through all of the datab connections and remove the space after the equals sign, so that, in the example above, Data Source= IG-SQL2017-01\GP... becomes Data Source=IG-SQL2017-01\GP....

Microsoft Dynamics GP 2018 R2 Displays Full Screen By Default

Microsoft Dynamics GPLast year Steve Endow did a post on Microsoft Dynamics GP 2018 always starts full screen and how you can stop it from doing so. The cause is a setting in the Dex.ini file which was set to TRUE:

WindowMax=TRUE

Prior versions of Dynamics GP had this setting set to FALSE; at the time he posed, Steve wasn’t sure if the setting was always set to TRUE or only if the Web Client Runtime was installed. Well, I can confirm that it is always set to TRUE.

I haven’t been that bothered by Dynamics GP always starting full screen, but after a client upgrade I was asked by them about it.

To stop Dynamics GP always starting full screen you need to change the Dex.ini file setting to false; this needs to be done on every client. If you are a GP Power Tools user you can use the Dex.ini Configuration tool to change all clients, otherwise you will need to manually update all clients.

Changing System Database Name After Installing the Microsoft Dynamics GP Client

Microsoft Dynamics GPI was installing a new VM to do some testing on and, after installing the Microsoft Dynamics GP, I ran GP Utilities and realised that I had an mistake in the system database name I had defined; the SQL Server I am using already had a deployment of Microsoft Dynamics GP 2018 R2 on it, so could not use my usual name of D18R2 and had to use an alternative.

I had decided to name the system database D18R2U and Fabrikam sample company as U18R2 as this demo VM was to be in US English. However, I named the system database U18R2.

I’ve never changed the system database used by a client before, but I remembered seeing a setting in the Dex.ini file:

Dex.ini file with Pathname line highlighted

Continue reading “Changing System Database Name After Installing the Microsoft Dynamics GP Client”

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Skip Displaying New POs When Generating a PO

Microsoft Dynamics GPThis post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.

This hands on new feature is, as far as I am aware, an unannounced one which I stumbled across when testing the partial purchase a purchase requisition new feature. When you click the Generate button on the Purchase Order Preview from Purchase Requisition Entry window, a prompt Skip displaying the new purchase orders? will be displayed:

Microsoft Dynamics GP - Skip displaying the new purchase orders?

This is a change of behaviour from the new functionality introduced in Microsoft Dynamics GP 2018 RTM; the purpose of this original new feature was to improve visibility of the created purchase orders.

This was, and remains, a laudable goal, but unfortunately the implementation was somewhat lacking. The new purchase orders were displayed by opening a navigation list, which could be ver slow to open (especially if the Reporting Services Reports had been deployed and the fact pane visible.

The 2018 R2 new feature, to hide Business Analyser for all users would go some way to mitigate this issue, by hiding the fact pane, but this new feature of prompting the user to decide if they want to see the navigation list will go the majority of the remaining way (a global option to disable would have gone all the way).

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Email POP PO Other Form

Microsoft Dynamics GPThis post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.

The twenty-third new feature is Email POP PO Other Form. This feature makes the Purhcase Order Other Form available for email.

My hands on with the feature was somewhat abbreviated when I discovered that there was no default Word Template available. While technically allowing a PO to be emailed using the Other Form, the lack of a default Word Templates means that there is a large amount of effort involved to make it available.

To create a new Word Template, you need to use the Word Template Generator to create a Word Template from the Report Writer XML and then format the resulting template; this is a long, complex and difficult to process to do in order not to break the template so email, or even the Word Template itself, doesn’t get broken.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Purchase Requisition Partial Purchase

Microsoft Dynamics GPThis post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.

The twenty-second new feature is Purchase Requisition Partial Purchase. You’ve always been able to increase the quatity to purchase, but you were not able to reduce the quantity. This new feature, allows a smaller quantity to purchase to be specified in order to partial purchase the requisition; the remaining quantity will be cancelled:

Microsoft Dynamics GP - The remaining quantity ordered will be cancelled.

The flexibility this offers should be a good thing, but I have concerns around users being able to change the purchasing quantity here if an approval workflow is being used. That said, I already had these concerns about users being able to increase the quantity post approval.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Ship To Address Retained by Customer Combiner

Microsoft Dynamics GPThis post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.

The twenty-first new feature is Ship To Address Retained by Customer Combiner. This feature will retain the ship to address when customers are merged using the Customer Combiner tool:

Customer Combiner and Modifier

I’ve tested this feature and compared it to the functionality in 2018 RTM, and I can’t tell the difference. The Ship To address of the destination customer, does not change in either version and the ship to address from both the source and destination customers are both available after the combine.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index