Over a year ago, October 2020 to be exact, I mentioned on a forum post that I have finally worked out how to cycle through a scrolling window using Dexterity code.
Being able to perform an action for each line in a scrolling window has been something that Microsoft Dynamics GP developers have been trying to do since VBA was added to version 4.0 of GP and Visual Studio Tools was added to version 9.0 of GP.
I promised I would blog about this technique … so read on for the details.
Community Summit Conference 2021, hosted by Dynamic Communities (DC) ran in Houston, Texas, USA last week from 12th to 15th October 2021.
I presented a session on Microsoft Dynamics GP development tools. Because I am still unable to leave Australia due to the pandemic border closures, the session was a pre-recorded video presentation.
Community Summit Conference 2021, hosted by Dynamic Communities (DC), is happening right now in Houston, Texas, USA until from 12th to 15th October 2021.
I am presenting a session on Microsoft Dynamics GP development tools as the first session of the day on Friday. As I am still unable to leave Australia due to the pandemic border closures, the session has been pre-recorded and will be run as a video presentation.
However, I will be online in a Microsoft Teams Meeting for the duration of the session and would love for anyone attending the conference (and those just interested in GP Development) to join me and others in the community for a chat and Q & A session.
As a follow on from yesterday’s article on how different languages can be used to drive the Microsoft Dynamics GP user interface, this article discusses the need to move away from the old Visual Basic for Applications (VBA) way of thinking. If you missed yesterday’s article, here is the link.
Now that VBA is “End of Life” and many sites are starting to use GP Power Tools – Developer Tools module to replace the VBA business logic with GP Power Tools triggers and scripts. However some developers are still trying to write code as though they were still limited by VBA rather than leveraging the more powerful capabilities of GP Power Tools and Dexterity.
Over the last couple of months I have been seeing a huge uptake on the sale and use of GP Power Tools – Development Tools module as more and more Microsoft Dynamics GP customer sites move their customizations away for the now “End of Life” Visual Basic for Applications (VBA).
This article explains some of the differences and techniques for the common method driving the user interface using code written in VBA, Dexterity and Visual Studio Tools (C# or Visual Basic .Net).
As promised in my previous article, this article contains awesome example GP Power Tools – Developer Tools projects for tracking changes to customer and vendor cards records.
Thanks to Eric Gernan from Amaysim Mobile whom I worked with to create this custom functionality and gave me permission to publish generic versions of the projects.
Back in 2017 I wrote an article which demonstrated how to get GP Power Tools to send an email every time the Credit Limit Field on the Customer Maintenance window was edited by a user and saved.
This article revisits this article by enhancing the functionality with the options to log changes to a text file or a SQL table instead of sending an email.
Dynamic Communities (DC), the team behind GPUG, will be hosting their Community Summit Conference on 12th to 15th October 2021. The agenda with sessions has now been posted online and I will be presenting a session on Microsoft Dynamics GP development tools.
I was recently asked how to use GP Power Tools to prevent users from Inserting or Deleting lines from the Sales Transaction Entry (SOP_Entry) window.
It is a really simple customization so I thought I would post it as a sample for your reference.
The Dynamics User Group (DUG) will be hosting its DynamicsCon Conference on 20th to 23rd September 2021. The agenda with sessions has been posted online after the session voting and selection has been completed and I will be presenting a session on Microsoft Dynamics GP development tools.
Today is the last day to vote for your favourite DynamicsCon conference sessions ahead of the conference scheduled for 20th to 23rd September 2021.
Make sure that you register and apply your 12 votes today to shape what you want to see at the conference.
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.
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.
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).
You might have seen yesterday’s article: #GPPT Processes are currently being run Dialog when logging into Microsoft Dynamics GP, which discusses a problem caused by a clash of a GP Power Tools build 28 feature and FastPath SSO (Single Sign On).
[Edit] FastPath have already released an update which fixes the issue. Thanks for the quick turn around.
The root cause of this issue is the undocumented side effect of using the Dexterity Activity_GetBackgroundStatus() command. Read on for the full explanation.