This article completes the creation of a GP Power Tools customization to prevent POP Receivings from updating the Originating Invoice Cost field on the Item Vendors Maintenance window.
Please make sure you have read the previous articles before continuing:
In the previous articles we used GP Power Tools to identify the table and field we want to work with as well as the script responsible for making the change to the field during the receivings posting process and then used triggers to restore the previous value of the field when posting receivings transactions.
This article continues the creation of a GP Power Tools customization to prevent POP Receivings from updating the Originating Invoice Cost field on the Item Vendors Maintenance window.
Please make sure you have read the previous article before continuing:
In the previous article we used GP Power Tools to identify the table and field we want to work with as well as the script responsible for making the change to the field during the receivings posting process.
I was recently working with a GP Power Tools customer who wanted to solve an issue with how the Purchase Order Processing (POP) module on their Microsoft Dynamics GP system functions.
They have international suppliers who specify the cost for their inventory items on a regular basis by sending through a price list document. Due to long lead times and shipping delays caused by the pandemic, cost pricing might change while the items are still in transit.
The issue is that when receiving a purchase order, the Originating Invoice Cost field on the Item Vendors Maintenance window is updated from the last received transaction, overwriting the current cost price provided by the supplier. The result is that subsequent purchase orders created have the incorrect cost value from the receivings transaction instead of from the supplier’s price list.
The Dynamics User Group have published the videos of the presentations from the recent DynamicsCon March 2021 event.
It was fun taking part in the conference and I really appreciated the opportunity to present for you. Thank you to the GP Community for voting for a session on GP Power Tools at the conference.
The DynamicsCon 2021 Virtual Conference starts today (it is already Tuesday for me in Perth, Australia). The free three day conference runs from Tuesday 16th March to Thursday 18th March 2021 (USEST).
Make sure you are registered for the conference and also planning to attend my “Leveraging GP Power Tools as a Consultant” session on Thursday 18th March at 11:00 am (USEST).
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).
I was asked recently to assist with some custom code that had been added to a transaction window in Microsoft Dynamics GP. The customization would work for one user, but not for a different user.
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).
I am writing this article after a good friend, who is a Microsoft Dynamics GP administrator, was having some unexplained issues in his test environment.
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.
Voting for the session submissions for the DynamicsCon virtual Conference closes om Friday 22nd January 2021 at 11:59 PM (US EST).
Please register for the conference and cast your 18 votes against the sessions you want to see presented. Not that I am biased, but please consider voting for some (or all) of the sessions I submitted.
The Dynamics User Group (DUG) will be holding its second DynamicsCon virtual conference on March 16-18 2021 and this time it includes Microsoft Dynamics GP content.
Submissions for proposed sessions has already closed and we are now in the voting phase where the community needs to vote for the sessions they would like to see in the final lineup.
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.
This week I received two similar requests and so I thought I would publish a couple of sample customizations which achieve the desired goals.
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.
There have been compatibility issues reported with sending emails via Outlook and more recently issues with VBA on Windows Server 2019.
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.
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 🙂.
The latest version of Microsoft Dynamics GP was released yesterday and it contains with 20 new features and 50 bug fixes. Winthrop Development Consultants has already updated its products for this Microsoft Dynamics GP – October 2020 release. They are now built against the final build and so are no longer beta builds.
Check out the previous article for more information:
Last Friday Terry Heley from the Microsoft Dynamics GP support and services team in Fargo, North Dakota emailed out a download of the upcoming Microsoft Dynamics GP release to the ISV (Independent Software Developer) community.
This “ISV Drop” is an early build which allows developers to start preparing to support the next version of Microsoft Dynamics GP. It give the GP developer community time to set up their development tools and environments for the new version.
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.