The customization was created using GP Power Tools‘ Developer Tools module, but similar code could have been created using Dexterity, Visual Studio Tools or even VBA (Visual Basic for Applications).
The issue was originally identified because GP Power Tools‘ Product Version Validation feature started reporting a dictionary version mismatch for a couple of Dexterity customization dictionaries. What made it really weird was that it only happened for the test windows’ user and and not for his administrator user account.
One of the really useful features of the Database Tools module of GP Power Tools is the ability to send Password Reset Emails to users when their passwords are reset.
These emails can be sent when updating the password manually via the User Setup window or automatically when using the Database Validation or SQL Login Maintenance windows of GP Power Tools.
Note: Build 28.3 or later is required for the functionality discussed in this article to work.
If you want to have a standard templates when adding Customer IDs and Vendor IDs, these two samples will provide that functionality with just a few triggers using the GP Power Tools – Developer Tools module.
In recent times many Microsoft Dynamics GP sites have been having issues with VBA (Visual Basic for Applications). Especially with Microsoft Office Updates breaking functionality and incompatibilities with later Windows Server releases.
So you have GP Power Tools installed on your system, how do you make sure that you are getting the most out of your subscription?
Firstly, make sure that GP Power Tools (GPPT) is installed on all workstations and servers. Everywhere the Microsoft Dynamics GP application is installed should have GP Power Tools installed.
Secondly, make sure you are running the latest build of GP Power Tools. Each build is released for the last five versions of Microsoft Dynamics GP and adds lots of new features, enhancements and fixes. Stay current to ensure you get what your subscription entitles you to. See this article for rolling out or updating GP Power Tools.
With the completion of development and release of Build 28 of GP Power Tools, now is the time to publish more examples for the Developer Tools module. Please see the GP Power Tools Samples page for additional examples that you can download and use for free.
This example is simple and can speed up data entry in Microsoft Dynamics GP. It does require GP Power Tools (GPPT) installed and the Developer Tools module registered. If you don’t have GP Power Tools installed or the Developer Tools module registered, feel free to install and start a free 30 day trial period, so you can test out this and the many other samples.
With the completion of development and release of Build 28 of GP Power Tools, there is now time to publish some of the great examples for the Developer Tools module. Please see the GP Power Tools Samples page for additional examples that you can download and use for free.
This example is amazing and every site with Microsoft Dynamics GP will want it installed. It does require the current Build 28.1 or later installed and the Developer Tools module of GP Power Tools (GPPT) registered. If you don’t have GP Power Tools installed or the Developer Tools module registered, feel free to install and start a free 30 day trial period, so you can test out this and the many other samples.
As promised, following on from the previous article: #Dexterity Automating or Customizing the Report Destination Window, this article shows how you can achieve the automating of the Report Destination dialogs using GP Power Tools – Development Tools module, including the dialogs in the Dexterity Runtime Engine.
Last month, nine well known Microsoft Dynamics GP ISVs (Independent Software Vendors) held the first Dynamics GP ISV Virtual Round Up.
The Round Up consisted of nine one hour presentations spread over two days and was offered free to the Microsoft Dynamics GP Community for both Partners and Customers.
Back in 2009, I posted about Automating or Customizing the Report Destination Window. In that article I discussed that there is more than one version of the Report Destination dialog and that additional methods would be required to control the version that is in the Dexterity Runtime Engine.
This article gets into more detail showing how the control the different dialogs with Dexterity.
Build 26 of GP Power Tools introduced a new Automatic Logout feature for Microsoft Dynamics GP. This functionality was further enhanced in Build 27 and again in the upcoming Build 28 release.
While there are other solutions which can log out inactive users, the implementation in GP Power Tools has many enhancements and features not available in other offerings.
However, there are also times when Automatic Logout has been reported not to work. Read on to understand what is happening….
In the last few blog articles I have mentioned that I am working hard on development of the next release of GP Power Tools Build 28.
Here is sneak peek at some of the features coming in the next build. There are already a number of sites using beta releases of Build 28 in their live environments making sure that everything is working perfectly.
We are hosting a free virtual conference with two half days of presentations called the Dynamics GP ISV Virtual Round Up.
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.
[Edit] This functionality is now built into Build 28 of GP Power Tools as an option in Administrator Settings.
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: