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.
