That’s correct, the year will no longer part of the version name for Dynamics GP. In fact version 18 will be the last version of Dynamics GP (in the same way that Windows 10 is the last version of Windows).
After attending the User Group Summit Australia conference in Melbourne in August 2019, I feel compelled to write another opinion article.
The conference was fantastic with over 600 attendees for the inaugural event with lots of great local and international presenters as well as many exhibitors and sponsors.
But the number of Microsoft Dynamics GP customer sites represented was extremely low and quite disappointing. After investing time and money to attend and exhibit at a conference, it feels like a missed opportunity when the target audience is barely represented.
Sorry about the click bait title, but it got you to read this opening paragraph. This article is my opinion on Microsoft’s current marketing strategy for its Dynamics accounting/ERP (Enterprise Resource Planning) product range and how, with a couple of minor changes, Microsoft can convert all of its Microsoft Dynamics GP customers to Microsoft Dynamics 365 solutions in due time.
To understand what the problem is and what the simple solution is … read on …
Have you ever had to do an upgrade of Microsoft Dynamics GP and the SQL Server has already been upgraded to the latest and greatest, but now when you attempt one of the upgrade steps, you get a SQL Version error for Dynamics Utilities.
The wording of the error message is along these lines:
Your current SQL Server is not a supported version.
Req: Microsoft SQL Server 11.0
Act :Microsoft SQL Server 20XX (RTM) – XX.0.XXXX.XXX
You need to upgrade to SQL Server 11.0 before continuing.
Earlier this month there was a thread on the Microsoft Dynamics GP community forum which described an issue where there were too many menu choices showing after logging into Dynamics GP.
The issue is not a bug, but standard behaviour in Microsoft Dynamics GP which was causing some confusion for users at the customer’s site.
As a follow on to the recent post : #GPPT Why every GP site needs GP Power Tools – Developer Tools, this article explains the benefits of replacing your VBA (Visual Studio for Applications) and VSTools (Visual Studio Tools for Microsoft Dynamics GP) customizations with GP Power Tools.
It has been prompted by the issues seen because the redistributable version of VBA that is packaged with Microsoft Dynamics GP has reached end-of-life as explained in the following article from the Microsoft Dynamics GP Support and Services team:
Another thread on the GPUG forum prompted me to write this article. It is one that I have been meaning to write for a while as this is not the first time I have seen complaints that a Dex.ini setting does not work or is not behaving as expected.
This article explains the changes made in the recent versions of Microsoft Dynamics GP and how they could be causing the behaviour you are seeing.