#GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 5

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:

• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 1
• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 2
• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 3
• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 4

The idea is to show how the helper functions simplify your code.

#GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 4

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:

• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 1
• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 2
• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 3

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.

#GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 3

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:

• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 1
• #GPPT How to improve Dynamics GP with a little bit of GP Power Tools – Part 2

#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.

#Dexterity Improving Performance on Windows 10

I often work with multiple instances of Dexterity open at the same time and export & import resources or cut & paste code between the instances.

Once I have everything updated, I usually Compile All to make sure that all the code is compiled and that there are no compile time errors. Don’t want any of those pesky “FP: Script Not Found” errors you get if you have saved but not compiled a script.

#Dexterity Well Behaved Ranges

While we are discussing ranges and in particular indexed ranges, it is worth having a discussion on what a “Well Behaved” range is.

If you have not read the previous article on Future Proof range setting, check it out below:

• #Dexterity Future Proof Range Setting