Click here to
Subscribe to
our Newsletter
One of the regular pieces of feedback I often hear from Microsoft Dynamics GP users is that they really wished that the application would remember where they want their windows positioned.
To solve this issue, in Build 22 of GP Power Tools, I added the Window Position Memory feature (released in February 2017).
Adding to this week’s series on customising the Payables Transaction Entry window using GP Power Tools, I thought it would be interesting to show some variants of the trigger script using less and less of the built in GP Power Tools features.
If you missed the previous articles please check them out below:
The idea is to show how the helper functions simplify your code.
Finishing this week’s series on customising the Payables Transaction Entry window using GP Power Tools, today we update the Trigger script and make everything work.
If you missed the previous articles please check them out below:
The final step is to update the Trigger script to perform the desired actions to check the last transaction date and open the Vendor Address Inquiry window.
Continuing with this week’s series on customising the Payables Transaction Entry window using GP Power Tools, today we create the Trigger and test it is working.
If you missed the previous articles please check them out below:
Following on from yesterday’s article: #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 1, let’s look at how this can be achieved using GP Power Tools.
I will be using the very latest GP Power Tools Build 23, Last Modified: 17-Mar-2018 Hotfix release as this includes new Helper Functions to make the use of parameters in scripts called programmatically much simpler to use.
I recently saw a post by my friend, Steve Endow, where he used a small Visual Basic for Applications (VBA) script to improve Microsoft Dynamics GP functionality.
So, I thought it would be worth showing how the same customisation can be achieved using GP Power Tools and its Developer Tools module, and explain the benefits of this approach over its VBA equivalent.
This is the fifth article in the #GPPT GP Power Tools: What’s in each module series? of articles.
It covers what is included in the Database Tools module. This module provides tools to backup and restore specific data as well as tools to ensure that your system is working perfectly with your SQL Server.
This is the fourth article in the #GPPT GP Power Tools: What’s in each module series? of articles.
It covers what is included in the Developer Tools module. This module provides extremely powerful, multi-lingual triggering and scripting capabilities that can be used to solve and fix bugs, create customizations or provide self-service support.
This is the third article in the #GPPT GP Power Tools: What’s in each module series? of articles.
It covers what is included in the Administrator Tools module. This module is a must for all Microsoft Dynamics GP sites as it makes working with and administering Dynamics GP simpler, easier and just better.
This is the second article in the #GPPT GP Power Tools: What’s in each module series? of articles.
This article covers the System Features. This module is included free of charge when you subscribe to any of the three chargeable modules. System Features includes many functions needed to support Microsoft Dynamics GP.
Read more »
This week, we are posting a series about GP Power Tools and what is in each of the modules.
This series is the result of feedback received during demonstration presentations where I was asked to provide more detail than the summary information on the GP Power Tools products page and portal page: http://WinthropDC.com/GPPT.
Read more »
Mekorma no longer distribute Visual Studio Integration Toolkit and cannot renew subscriptions for the product.
Winthrop Development Consultants now distribute Visual Studio Integration Toolkit directly. To ensure a smooth transition, all existing sites will need to upgrade to build 12 or later before their subscription with Mekorma expires.
Updated builds for all Winthrop Development Consultants products were released in November 2017.
Winthrop Development Consultants are proud to release updated builds for GP Power Tools, Batch Posting Service Toolkit and Visual Studio Integration Toolkit. These builds include fixes and enhancements as well as a new registration system and an automatic check for updates.
Important Note: Please update all your installed Winthrop Development Consultants products at the same time. Failure to do so will cause products not updated to be unregistered.
I was recently asked whether GP Power Tools can be used to set a default value on a window. The answer is a very definite “Yes!”.
In fact, this sort of customisation is extremely simple with GP Power Tools and is just the tip of the iceberg for what is possible. Because we have access to Dexterity, Transact-SQL, Visual C# and Visual Basic.Net from inside GP Power Tools, the possibilities are endless and limited only by your imagination.
Also, you have the benefits of instant deployment once the triggers and scripts are enabled and saved, and everything works just fine in the Microsoft Dynamics GP Web Client too.
If you want to do any reporting on Microsoft Dynamics GP application level security from the SQL Server level, you need to use the Security Resource Descriptions (SY09400) table to map the Resources Type, Dictionary ID and Security/Resource ID to actual named resources that make sense to humans.
I have often seen questions raised about why some systems have all the resources listed in this table and other systems only have a subset of the resources or the table is empty.
With the addition of Service Based Architecture (SBA) into Microsoft Dynamics GP 2015 and later, Dexterity global procedures can be marked as Service Enabled.
This allows a Dexterity global procedure to be a Service procedure which is exposed as a REST based web service via Service Base Architecture.
While at GPUG Summit in Nashville, TN, USA in October, I came to an interesting realisation. I did mention this during one of the sessions I presented, but I wanted to write an article to reach a wider audience.
It suddenly dawned on me “Why I continue to develop GP Power Tools”.
Following on from yesterday’s article: Visual Studio Tools: Best Practice when adding References to Projects, I wanted to highlight that all of Winthrop Development Consultants product installers have been updated to help avoid the problems caused by duplicate old DLL files in the Addins folder.
This issue is most likely with Visual Studio Integration Toolkit where developers use the toolkit from their products by adding the reference to the Dictionary Assembly DLL file.
I love writing these sorts of articles. My good friend and fellow MVP, Mariano Gomez, has been using GP Power Tools to assist him in his role as Development Manager at Mekorma and has written blog articles about his experiences.
GP Power Tools removes much of the complexity and time needed for Cross Dictionary development in Dexterity.
This article is an informational post to help anyone who might have come across this issue with Integration Manager and is searching online for a solution.
The issue is Integration Manager only imports a few transactions before failing when using the Standard Adapters for some integrations.
One possible cause for this issue was fixed many months ago in GP Power Tools code, but as not all sites keep up to date with their software, it might still be occurring. A recent support case for this issue is the reason for publishing this article.