Today I was asked about how you can use Dexterity to create SQL Stored Procedures when the stored procedure itself exceeds 32,768 characters.
This 32K limit is because the largest datatype supported by Dexterity is the Text field which is limited to 32,768 characters. This is the maximum size of a signed 16 bit integer (-32767 to 32768).
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.
The GPUG Summit 2018 Conference is fast approaching. It is being held on October 15-18, 2018 at the Phoenix Convention Center, Phoenix, Arizona, USA.
Winthrop Development Consultants will be at the conference as I am training 3 GPUG Academy classes and co-presenting at least 5 sessions. We will also have booth 1540 at the Expo.
Register now before the early-bird pricing runs out on September 6th… Don’t forget to use the Winthrop 10% discount code below.
We are getting to the 2018 conference season again, and it is time to take advantage of the pre GPUG Summit Dexterity training that is being run in the week prior to GPUG Summit 2018 in Phoenix, Arizona, USA.
Dexterity is the development environment that Microsoft Dynamics GP is built on and the best tool to use for any customisation to the user interface of the product.
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:
