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:
SQL Server
#GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 2
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.
#GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 1
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.
#GPPT GP Power Tools build 23 released
I am pleased to announce that the next build of GP Power Tools for Microsoft Dynamics GP (GPPT) is now available for download.
GP Power Tools is the industry leading suite of tools to designed to make your Microsoft Dynamics GP life simpler and easier. Features have been specifically designed and created to enhance the user experience, simplify the administrator experience and provide power debugging and customisation tools to consultants and support engineers.
This is why GP Power Tools should be installed on every workstation of every Microsoft Dynamics GP system globally.
#GPPT GP Power Tools Demonstration Video
Thanks to Kim Peterson from Dynamics Connections, I am pleased to release a new video demonstration of Winthrop Development Consultants’ GP Power Tools (build 23).
Watch to learn why every Microsoft Dynamics GP site globally should have GP Power Tools and why many partners now install GP Power Tools as part of their standard installation.
#SQLServer Working with Dexterity Dates and Times in Transact-SQL
When Dexterity was first implemented on SQL Server for version 3.15, there was a number of decisions made on how to map the datatypes, fields and tables designed for ISAM platforms such as Ctree and Btrieve/Pervasive SQL to work on SQL Server.
One of the decisions was how to map the individual date and time control types to work with the datetime datatype in SQL Server.
#GPUGSummit Developers at GPUG Summit
Hey Developers… Are you attending the GPUG Summit 2017 conference in Nashville, Tennessee in October? If so, this article is to let you know about Microsoft Dynamics GP related Developer content at the conference.
I asked why there was not much content for developers at GPUG Summit and I was told that there are not many developers in attendance. I disagreed and requested a session for Developers, which Bob McAdam promptly organised … thanks Bob. 🙂
#Dexterity Development Environments – Part 1: Installation
This article has been a long time coming and is the first of a series of articles on how I set up my machine for developing Dexterity applications across multiple versions.
I promised I would detail how my system is set up a while back at the reImagine 2015 conference and had never got around to writing the article until now.
#FabrikamDay How to quickly update the sample data to 2027
In case you missed it, yesterday was Fabrikam Day for the Microsoft Dynamics GP community. This was the 12th April 2017, the date that the sample company’s, Fabrikam, data is based around.
For more information about Fabrikam Day and the sample company have a look at my article from yesterday:
Identifying Triggers registered against a Table
Last week, I wrote about a situation which was causing issues with the Database Validation feature of GP Power Tools. Triggers on the ACTIVITY table that fired when records are deleted that attempt to clean up data in the company that the record is related to.
The problem is that if the current user does not have access to this company or company database does not exist or is not online, errors are generated and the code fails. This is discussed in my blog:
Delete or Remove Range Errors on ‘SY_Current_Activity’ table after GP 2015 R2
Microsoft Dynamics GP 2015 R2 added lots of new features and enhancements and fixed a number of bugs too. However, it also introduced a change that is now causing errors in some ISV’s (Independent Software Vendor) products.
I first came across this issue when preparing to release GP Power Tools build 22 and was testing the Database Validation feature on my Microsoft Dynamics GP 2016 install.
#GPPT Adding data from any SQL table to SOP Documents
Following on from my recent article, #GPPT Adding Vendor Item Number to SOP Documents, I thought it would be worth showing how we can use GP Power Tools custom Report Writer RW functions with a SQL Query to obtain any data available from any table on the SQL Server.
To make this happen we are going to combine the Runtime Execute Setup custom RW function code with a SQL script created in SQL Execute Setup. Note that these techniques, which have been available since June 2009, are completely Web Client compatible which makes them even more valuable now.
Handy Developer and Administrator Tools
I want to make everyone’s life easier.
I should clarify that this is life in respect to my work life. As a Developer, IT Professional and Microsoft Dynamics GP Consultant I love anything that makes my job easier.
That’s why I created GP Power Tools (formerly the Support Debugging Tool) in the first place.
Friday Funny: Exploits of a Mom
My good friend, Belinda Allen MVP, sent a funny comic strip from xkcd to me last week.
I thought it needed to be shared as it is funny to the database administrators and developers among us, but also highlights an important issue.
Using the Support Debugging Tool to create user accessible SQL Scripts – Part 3
This is the third and final article in the series, make sure you look at the previous articles before this one.
The previous articles can be found at:
- Using the Support Debugging Tool to create user accessible SQL Scripts – Part 1
- Using the Support Debugging Tool to create user accessible SQL Scripts – Part 2
Today’s article adds the final step by adding a method for a user to execute the code we have written so far without requiring access to any Support Debugging Tool windows.
Using the Support Debugging Tool to create user accessible SQL Scripts – Part 2
This is the second article in the series, if you haven’t already, please see the previous article: Using the Support Debugging Tool to create user accessible SQL Scripts – Part 1.
Today’s article adds a simple user interface for the previously created SQL scripts using Dexterity sanScript.
Using the Support Debugging Tool to create user accessible SQL Scripts – Part 1
It has been a while since I have posted a technical article on the blog. This is because I am spending almost all my time working on bringing some existing and new products to market.
I am still working on the rebranded and improved release of the Support Debugging Tool. There will be a number of improvements in its features and navigation, more on that soon.
For now, I wanted to post a really clever method of using the Support Debugging Tool to provide additional functionality to end users.