Over the last few weeks I have been chatting with Terry Heley on the Microsoft Dynamics GP Support team. She was been working really hard on getting the Lifecycle information for Microsoft Dynamics GP updated to reflect Microsoft’s ongoing commitment to the Dynamics GP product.
Regardless of of the sales hype and disinformation you might hear from other sources who want to spread FUD (Fear, Uncertainty and Doubt), Microsoft Dynamics GP is not going away any time soon and the product lifecycle information has been updated to show this.
Over the last week, there has been a Microsoft security update released via Windows Update which is causing graphics on Microsoft Dynamics GP Report Writer reports to show as black boxes.
The Microsoft Dynamics GP support team is aware of the issue and is working to find a resolution. The current work around is to roll back the Windows Updates that caused the issue and pause updates to prevent them from being installed again.
[Edit] 20-Mar-2021: The Windows team have released a fix for this issue, it look’s like it needs to be installed manually. Please see the updates on both the articles from the Dynamics GP Support team and from Beat Bucher (links below).
Back at the end of July, I had the opportunity to be interviewed by Mark Smith from New Zealand (also known as the nz365guy) for his MVP Show podcast series.
This was the first time I have been interviewed for a podcast and it was a great experience. Still waiting for the Enterprise Software Podcast team… Hint, Hint, Bob 🙂.
This article comes about because we have identified a feature of GP Power Tools that does not work as expected on the Web Client. GP Power Tools has the ability to run scripts and register triggers against Modifier added fields and Modal Dialogs. These features uses the Dynamics.Application object and in particular a suite of functionality historically known as “Continuum”.
We can now confirm that the Dynamics.Application object is not available at all when running Microsoft Dynamics GP in the Web Client and so any functionality reliant on this object will fail to work.
This is an issue that I found back in April 2019 and reported to Microsoft. I added it to my list of articles to write up where it sat until today. Now that I have seen it happen “in the wild” and not just on my test system, I thought I better spend some time to get it documented.
The error occurs when launching Microsoft Dynamics GP and can happen on any version since about v8.0. When you launch GP it displays the Dexterity Login Dialog and if you don’t log in, it will generate a couple of error dialogs.
Guess what? … there will be no Microsoft Dynamics GP 2018 R3, Microsoft Dynamics GP 2019 or Microsoft Dynamics GP 2020. Why? Because in early October 2019, we will have Microsoft Dynamics GP instead.
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 …
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.
This is a reposting of an article Viswanathan Neelakantan originally wrote on my Developing for Dynamics GP blog.
Recently there was a question on the forums regarding passing parameters to custom SSRS reports assigned to Dynamics GP windows.