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:
Following on from my recent article, #GPPT Adding Vendor Item Number to SOP Documents, I thought it would be worth showing how we can use GP Power Tools custom Report Writer functions with a SQL Query to obtain any data available from any table on the SQL Server.
To make this happen we are going to combine the Runtime Execute Setup custom RW function code with a SQL script created in SQL Execute Setup. Note that these techniques, which have been available since June 2009, are completely Web Client compatible which makes them even more valuable now.
In my previous post, RW: Using the rw_TableLineString() and rw_TableLineCurrency() Report Writer functions, I mentioned the six report writer functions which can be used by developers to get custom data onto reports.
GP Power Tools takes advantage of these functions to allow the creation of custom Report Writer functions. In fact, this custom report writer function feature has been available since the release of the Support Debugging Tool build 11 in June 2009.
When Microsoft Dynamics GP 9.0 was released, it included six new global functions specifically added to make life easier for ISVs (Independent Software Vendors).
These six placeholder functions were added so that Dexterity developers could trigger against them and use the functions to get their custom data on to reports without needing to create alternate reports.
Welcome to 2017. I hope you all had a fantastic time over the Christmas and New Year period.
If you have studied software development or computer programming, I would be surprised if you did not at some stage cover sorting algorithms.
I want to make everyone’s life easier.
I should clarify that this is life in respect to my work life. As a Developer, IT Professional and Microsoft Dynamics GP Consultant I love anything that makes my job easier.
That’s why I created GP Power Tools (formerly the Support Debugging Tool) in the first place.
I came across an interesting issue yesterday when I installed Microsoft Dynamics GP 2016 and its matching Dexterity 16.0 version.
When installing Dexterity I received an error message which in turn caused the installation process to be cancelled.
Note: We have skipped version 15.0, so that GP 2016 is version 16.0. This avoids the confusion we have had previously with the version “year” not matching the version “number”.