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. 🙂
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.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Following on from my post: Microsoft Dynamics GP 2013 R2 updates to Report Writer Functions, I have to admit that I made a mistake.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
You might remember the story about how I created a suite of Report Writer functions and got them added to the version 7.0 Dynamics.dic core dictionary. The aim for these functions was to make it easier for partner consultants and customers to modify the reports without needing custom scripting in Visual Basic for Applications (VBA) or Dexterity. They are documented in the Report Writer Functions document in the Software Developers Kit (SDK).
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Microsoft Dynamics GP 2013 added a long awaited feature, the ability to change the printer selection for a report after it has printed to the screen output.
