Recently Steve Endow MVP asked on Twitter if there was a simple solution for moving SOP Transactions from one batch to another batch.
This is something that is easily solved as a Self Service script using the GP Power Tools – Developer Tools module. In fact, I had already created a solution for the same request for a customer in Australia using GP Power Tools. I spoke to the customer, Anand, and he said he was happy for me to post the code on the blog.
Today, we have an article from guest author Craig Verster, Senior Microsoft Dynamics GP Consultant at Microchannel Services, who identified an issue that can affect Australian (and potentially other non-US) SQL Server installations.
When installing SQL Server Database Engine the default collation is dependent on the Locale of the operating system.
i.e. If Australia, then Latin1_General_CI_AS is the default collation method.
If USA (which is the default locale), then SQL_Latin1_General_CP1_CI_AS is the default collation method.
Although both these collation methods use code page 1252 they actually work very differently.
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.
