This blog article has been prompted by the thread below on the Microsoft Dynamics GP community forum:
I had responded with some information on the thread, but when I tried to implement the suggestions I made, I found that it was not actually possible and that other methods would be needed.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I have completed the development project I was working last week and have another Quick Tip that came out of the project. For the previous Quick Tips related to this project have a look at Quick Tip: Passing Variables to SQL Server and Quick Tip: Passing Date and Time Variables to SQL Server.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I have had a couple of recent cases which highlighted the importance of selecting the correct Key fields when creating Extender objects. Both of the cases involved adding additional user defined fields to an existing Microsoft Dynamics GP window using an Extender Window Object. In both cases, the incorrect fields were selected in the Key Fields section of the Extender Windows setup window which caused undesired behaviour.
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.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
An Extender case came up recently where the customer was having security issues with Extender forms.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
You might remember last month when we had a support case where the customer wanted to use Extender additional information against the General Ledger Journal Entry (GL_Transaction_Entry) distribution lines.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Last week I had an interesting support case that I thought I would share with you.
The customer had created an Extender window to capture additional information for distribution lines on the General Ledger Journal Entry (GL_Transaction_Entry) window. The unique identifier for a distribution line is the Journal Entry field from the main window and the Sequence Line field from the scrolling window. These are the fields used when creating the Extender settings for the additional information to be stored.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Last week, I tackled the subject of orphaned records in the Extender tables when the parent records were deleted and the Extender data was left behind. If you have not read this post the link is below:
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I was recently asked to assist a colleague with an Extender case. The problem was that Extender data was not being removed from the Extender SQL tables when its parent record was deleted.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Extender can create SQL views of the data in an Extender window which allows the data to be viewed as a single row in the view even though the actual data is stored as a multiple records across multiple tables (depending on data type).
This view can then be used by SmartList Builder to show the Extender data in SmartList.
