Following on from last week’s GPUG Amplify conference, Pam Misialek has released an updated version of the Microsoft Dynamics GP Product Roadmap as at March 2017. While I was unable to attend the conference, I heard that it was a success!
This corrected slide has fixed some minor errors that were on the slide presented at the conference (oops).
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:
Hi everyone out there in GP land.
Thanks for the very positive feedback I am receiving for GP Power Tools Build 22. It seems like the new features and enhancements are being appreciated by the Microsoft Dynamics GP community.
Make sure you try out Deny Based Security and Window Position Memory as these are features every Dynamics GP customer can use.
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.
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.