I have posted several articles recently about the truth behind D365.
The nutshell is that Dynamics BC is not the “next version” of GP. If you decide to go down that path it is implementing a new ERP software package from scratch. Do you remember how fun that was when you went live with GP? Do you want to do that again?
In this post I’m going to address the other side of the equation, because staying on GP is not without risks.
I’ll tell you a little fact about WilloWare. We still use an application for source code management called Visual Source Safe. It tracks a copy of every change to a module. This is invaluable because we can look back in time to see when a specific change occurred and what the software used to look like. It allows us to easily transfer a project between developers or bring a very old project back to life when somebody upgrades from say GP9 to GP2018! Its last supported release was 2005. We have a plan in place for what to do should it quit working at some point, and there are other options, but there is no benefit to WilloWare to change to something else.
Over the coming years there are a number of changes Microsoft could make to Windows and/or SQL Server that could render GP difficult or impossible to use, and only Microsoft would have the ability to fix GP.
They could change something in Windows (graphics, fonts, file system, file naming, registry, user interface elements like dropdown lists or buttons, printing), or SQL server (ODBC, deprecating commands). They would not intentionally “turn off” GP, but in the course of them evolving Windows and SQL Server something in GP could quit working.
We are already seeing a real-world example of this. If you use Remote Desktop published apps you have likely encountered the “missing buttons and checkboxes” issue. The first screen shot shows Manufacturing Order Entry as it should appear and the second shows how it appears as a published app.
The buttons and checkboxes are still there and still work, but the graphics are not working correctly so the outlines are gone (or can click on the invisible button and it works). Dynamics GP is still supported by Microsoft but this issue that started with Windows Server 2019 remains unresolved as of 3-NOV-2025.
FYI: Suggested Resolutions from Microsoft (we have not seen any of these work).
The core issue is that the Dynamics GP executable (dynamics.exe) dates back to the early 1990s and uses GDI (Graphics Device Interface) for rendering – a Windows graphics API designed for the era of CRT monitors and fixed DPI displays. Dexterity windows and controls do not have native DPI awareness built into them, which is why GP has no display settings of its own and completely relies on Windows OS behavior.
Even as a GP Source Code Developer, WilloWare does not have the ability to change the executable (or any of the DLLs used by GP). Which means a fix for this display issue requires Microsoft to change the executable.
There’s an old saying about wanting a one-handed lawyer to avoid getting “on the other hand….” advice. I’m not a lawyer, and I do have two hands.
On one hand, implementing a new ERP software package, like Dynamics BC, is a big task with real costs in dollars, time and productivity. On the other hand, using GP long term has unquantifiable risks that may or may not occur.
No matter what you decide WilloWare will be there for you on both Dynamics GP and Dynamics BC.
(Bonus trivia: Which product is older-Dynamics GP or Dynamics BC/NAV? Dynamics BC/NAV was released in 1985. Dynamics GP 1.0 was released in 1993).