Click here to
Subscribe to
our Newsletter
Over the last few weeks I have been asked about the same issue a few times by different customers and partners who were unable to work out what was happening.
So, I thought I would write an article that explains the problem and the solution and hopefully, it will show up when someone does a search when they have this issue.
The next installment of DynamicsCon conference is scheduled for 20th to 23rd September 2021. The session submission period is over and now we enter the session voting period until 28th July.
During this voting period all registered attendees have 12 votes to apply to sessions as they wish, then the votes will be tallied and the final session lists published. See this explanation for more details of the process.
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.
The recent Build 28.8 hotfix of GP Power Tools incorporated some Developer Tools module changes to enable so very cool customization options for updating reports based on temporary tables. The big feature enhancement is the ability to store a Table Reference as a Memory parameter.
References in Dexterity are like pointers to a particular resource, so the Table Reference allows access to the particular instance table buffer without needing to pass the table as a parameter to a script.
Here is another simple customization I thought it would be worth publishing because it allows us to discuss some best practices and also show some cool techniques.
I received an email from a user who wanted to use GP Power Tools to replace some VBA (Visual Basic for Applications) code using GP Power Tools. They wanted to update a SOP (Sales Order Processing) Sales Transaction Entry User Defined Field based automatically but the code they had developed was not working.
I was recently informed of an issue that a Microsoft Dynamics GP customer site was facing where having more than one user in a particular window at the same time was causing issues.
While the issue has been logged with Microsoft Support, the fix will not be available for a while, so I was asked how easy would it be to force the window to only work exclusively for a single user at a time using GP Power Tools.
The answer…. very easy …. initially.
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.
Today, I was asked by a partner how simple it would be to default the Sort by fields on the Payables Transaction Inquiry – Vendor window to Document Date in Descending order. This is previously the type of quick tweak that you might have used VBA (Visual Basic for Application) for.
However, now that VBA is “End of Life” and is not supported on the Web Client and some windows platforms, this is a perfect customization to use the GP Power Tools – Developer Tools module for. The entire customization took me about two minutes to complete. In fact, it took much longer to write this article.
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.