#Dexterity Remember Multicurrency when Customizing Transaction windows

I was asked recently to assist with some custom code that had been added to a transaction window in Microsoft Dynamics GP. The customization would work for one user, but not for a different user.

The customization was created using GP Power Tools‘ Developer Tools module, but similar code could have been created using Dexterity, Visual Studio Tools or even VBA (Visual Basic for Applications).

#Dexterity command Activity_GetBackgroundStatus() kills background Timed Processes

You might have seen yesterday’s article: #GPPT Processes are currently being run Dialog when logging into Microsoft Dynamics GP, which discusses a problem caused by a clash of a GP Power Tools build 28 feature and FastPath SSO (Single Sign On).

[Edit] FastPath have already released an update which fixes the issue. Thanks for the quick turn around.

The root cause of this issue is the undocumented side effect of using the Dexterity Activity_GetBackgroundStatus() command. Read on for the full explanation.

#GPPT Automating or Customizing the Report Destination Window

As promised, following on from the previous article: #Dexterity Automating or Customizing the Report Destination Window, this article shows how you can achieve the automating of the Report Destination dialogs using GP Power Tools – Development Tools module, including the dialogs in the Dexterity Runtime Engine.

#Dexterity Fixing the Properties Window width

A recent post on the GPUG Forums by my friend David Morinello asked how to fix the issue when the Dexterity Properties window resizes to smaller than its default width.

See the thread here: Dexterity Property Window too narrow

#Dexterity Automating or Customizing the Report Destination Window

Back in 2009, I posted about Automating or Customizing the Report Destination Window. In that article I discussed that there is more than one version of the Report Destination dialog and that additional methods would be required to control the version that is in the Dexterity Runtime Engine.

This article gets into more detail showing how the control the different dialogs with Dexterity.

#GPPT Converting .Net Execute Scripts from C# to VB.Net

Following on from the previous articles: #GPPT Speeding Up Referencing Modifier Added Fields and staying Web Client compatible and #GPPT Referencing Modifier Added Fields in the Web Client using .Net Execute, this article looks how we can use VB.Net rather than C# as the scripting language in the .Net Execute scripts.

Both VB.Net and C# use the .Net Common Language Runtime (CLR) and it is usually possible to write exactly the same code in either language. So we will duplicate our existing C# scripts and convert them to VB.Net, then we will duplicate the triggers to call the new scripts.

#GPPT Speeding Up Referencing Modifier Added Fields and staying Web Client compatible

Using the method discussed in the article #GPPT Referencing Modifier Added Fields in the Web Client using .Net Execute it was possible able to get past some of the limitations mentioned in the article Dynamics.Application Object not available on Web Client.

However, running the .Net (C# or VB.Net) code is slightly slower than running the Dexterity (sanScript) code. This article explains a method of how to improve Desktop Client performance while staying compatible with the Web Client.

#GPPT Referencing Modifier Added Fields in the Web Client using .Net Execute

You probably saw the recent article: Dynamics.Application Object not available on Web Client where I described an issue that was recently discovered and meant that the “Continuum” based triggers and scripts used to reference Modifier Added Fields in GP Power Tools – Developer Tools module were unable to work in the Web Client.

I mentioned a workaround that would function with the current GP Power Tools code when running on the Web Client (and Desktop Client). This article will show how you can use scripts in the .Net Execute Setup window to reference Modifier Added Fields.

#GPPT Disabling Manual Entry of SOP Number Field

Recently on the GPUG Open Forum, Jeff Roe asked if it was possible to disable manual entry by users into the SOP Number field on the Sales Transaction Entry (SOP_Entry) window.

I suggested using GP Power Tools – Developer Tools module to create a quick trigger to lock or disable the field. As Jeff is already a GP Power Tools user and has the Developer Tools module registered, I created the required code and posted it on the forum thread. Here is a slightly more detailed version of the forum response.

#GPPT Reporting for Minnesota’s Wage Theft Law

This article is comes about thanks to my friend, Melissa Brown, who approached me for a solution to a reporting requirement she had for a customer due to new legislation brought in by the US state of Minnesota.

The requirement was not possible to solve with the Dynamics Report Writer alone as it involved an array in a table which prevented a static relationship from working to retrieve the data needed.

#GPPT Dexterity Samples for Datatype Conversions

The previous article: #GPPT Parsing Returned SQL Data into Rows and Columns had some examples of how to convert string representations of various datatypes back to their native datatypes.

With GP Power Tools, it is a common technique to store additional data in the DUOS (Dynamic User Object Store) table (SY90000). However, the DUOS uses a 132 character string field to store the data and so datatype conversions in both directions will be needed.

#GPPT Parsing Returned SQL Data into Rows and Columns

When writing customizations using GP Power Tools as your development tool, there may be times where you need to return a SQL query as a data set to your Trigger Setup script or Runtime Execute Setup script.

It is possible to display a data set to the end user in a SQL Results window using the MBS_SQL_Results helper function. If you have “Goto” actions defined, the MBS_SQL_Results_Goto helper function will display the data and enable the SQL Goto functionality.

But what if we don’t want the data displayed to the user and just need to use the data in your code.

#GPPT Unknown Identifier Error when working against Modified windows

Dexterity is the native language of Microsoft Dynamics GP. It is an amazing development environment that is still the best and most powerful tool to integrate with the Dynamics GP User Interface. While Dexterity was originally developed in the late 1980’s, it has been continuously developed and extended with more and more features and functionality which allow it to handle everything needed for modern business applications AND still be completely backwards compatible to its original release.

However, Dexterity does have some limitations: It is a little bit more complex if you need to integrate with other third party dictionaries and it cannot work with modified windows. GP Power Tools extends Dexterity’s scripting capabilities to make it possible to easily work with multiple dictionaries and with modified windows.

#GPPT Beginner’s Guide to Adding Custom Fields – Video Demonstration

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:

• #GPPT Beginner’s Guide to Adding Custom Fields – Introduction

In this article we will put everything in the previous articles together in a video demonstration of the steps.

#GPPT Beginner’s Guide to Adding Custom Fields – Publishing the project

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:

• #GPPT Beginner’s Guide to Adding Custom Fields – Introduction

In this article we will adjust security and GP Power Tools settings to publish the customization to all users.

#GPPT Beginner’s Guide to Adding Custom Fields – Modifying the report

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:

• #GPPT Beginner’s Guide to Adding Custom Fields – Introduction

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.

#GPPT Beginner’s Guide to Adding Custom Fields – Creating the RW function

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:

• #GPPT Beginner’s Guide to Adding Custom Fields – Introduction

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.

#GPPT Beginner’s Guide to Adding Custom Fields – Using the data

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:

• #GPPT Beginner’s Guide to Adding Custom Fields – Introduction

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.

#GPPT Beginner’s Guide to Adding Custom Fields – Saving the data

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:

• #GPPT Beginner’s Guide to Adding Custom Fields – Introduction

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.

#GPPT Beginner’s Guide to Adding Custom Fields – Modifying the 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:

• #GPPT Beginner’s Guide to Adding Custom Fields – Introduction

In this article we will use Modifier to add the custom field to the Item Maintenance window.