Welcome to the eighth and final article in the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will put everything in the previous articles together in a video demonstration of the steps.
Welcome to the seventh article in the series of articles that explain in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will adjust security and GP Power Tools settings to publish the customization to all users.
Welcome to the sixth article in the series of articles that explain in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will use Report Writer to modify the Detailed Item List report to add a calculated field which in turn calls the custom RW Function created in the previous article.
Welcome to the fifth article in the series of articles that explain in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will use GP Power Tools to create a custom Report Writer (RW) function which will allow our custom URL field to be easily added to reports in the Report Writer.
Welcome to the fourth article in the series of articles that explain in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will use GP Power Tools to add the business logic to make the URL field work. We will make the hidden button open the URL in a browser window and add http:// at the beginning of the URL field if it is not added by the user.
Welcome to the third article in the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will use GP Power Tools to add the business logic to save the data from the newly added custom field on the Item Maintenance window.
Welcome to the second article in the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will use Modifier to add the custom field to the Item Maintenance window.
Welcome to a series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic. The example project will only need six scripts and no external development tools will be required.
The aim of this series is to work through each of the parts of the process and explain with step by step instructions how it works and why various settings are used.
It would be possible to just show the final result, but I want this series to serve as a guide for creating similar customizations in your own system. That said I will provide the final customization files at the end of the series.
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 RW 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 RW 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.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
My great friend, Leslie Vail – The Dynamics Confessor, has released a great series of posts about the Report Writer functions available in Microsoft Dynamics GP.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
There is an unsupported method of copying report formats between reports that is very commonly used (and even recommended by me), but we recently had a case that highlighted a problem with the technique. This blog post will discuss the method and the issue we have seen.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
My great friend Mariano Gomez, The Dynamics GP Blogster, has been busy recently creating some fantastic step by step posts on customising reports using Report Writer.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
As a Dexterity developer, I have written a number of customisations to Microsoft Dynamics GP which add additional fields to the system. These additional fields are often have a relationship to existing data in Dynamics GP.
It is quite common to store the additional data in a parallel table (sometimes called companion or shadow table). This is a table having same primary key as an existing table, with the additional fields.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Here is another support case that was resolved simply and quickly using the Support Debugging Tool.
The customer was using Extender to add an additional comment to the inventory stock transfer transaction. They created an Extender ID “ST_COMMENTS” and used the Long String field type in Extender which is a 255 character string. This worked fine.
