This article is comes about thanks to my friend, Melissa Brown, who approached me for a solution to a reporting requirement she had for a customer due to new legislation brought in by the US state of Minnesota.
The requirement was not possible to solve with the Dynamics Report Writer alone as it involved an array in a table which prevented a static relationship from working to retrieve the data needed.
When writing customizations using GP Power Tools as your development tool, there may be times where you need to return a SQL query as a data set to your Trigger Setup script or Runtime Execute Setup script.
It is possible to display a data set to the end user in a SQL Results window using the MBS_SQL_Results helper function. If you have “Goto” actions defined, the MBS_SQL_Results_Goto helper function will display the data and enable the SQL Goto functionality.
But what if we don’t want the data displayed to the user and just need to use the data in your code.
Earlier this week, a forum post by my friend Abra Gilman on the GPUG Open Forum brought up the problem where a user was getting an error when attempting to insert a new line into a SOP Transaction.
This problem can be reproduced by attempting to insert lines in the same location more than 14 times, on the 15th attempt an error will be generated.
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).
You might have seen my posts on Twitter and Facebook recently about my new toy mini laptop PC, the crowd funded GPD Pocket 2.
I have been burnt before with crowd funded projects (I supported 3 smartwatches and only one make it to production and it under-delivered 😦 ), so I was wary of getting involved again. However, this was the second generation of the GPD Pocket and demo devices had already been delivered to a number of YouTube reviewers. I felt fairly safe to get involved with crowd funding again, as this would give me a discount and get the device earlier.
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.
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.
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.
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.
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. 🙂
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.
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:
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:
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.
