Category: GP (Great Plains)

This post is part of the Hands On With the GP Power Tools (GPPT) – System Module series in which I am taking a hands on look at the varioues tools offered by GPPT.

In the last post, I gave an overview of the Manual Logging Mode and mentioned that the SQL Profile Tracing tool needs to be configured before it can be used.

There are recommend settings for the SQL Profile Tracing, which are configured as follows in this post.

The first step is to create a folder on a local drive of the SQL Server to store the traces as they are being produced:

I have created a folder called Dynamics Central and then a sub folder called SQL Profile Tracing as there are other files which will be shared with users.

Continue reading “Hands On With the GP Power Tools – System Module: Configuring SQL Profile Tracing With Recommended Settings”

This post is part of the Hands On With the GP Power Tools (GPPT) – System Module series in which I am taking a hands on look at the various tools offered by GPPT.

The first tool is the Manual Logging Mode. This tool allows easy enabling of several types of logging:

1. SQL Logging – SQL Logging tracks all communication between the Microsoft Dynamics GP client and the SQL Server. The default file in which the SQL communication is stored is named DEXSQL.LOG.

   When enabled, SQL Logging is on a workstation basis. On a standalone PC, this logging is easy to use and interpret, but on a terminal or Citrix server, all instances of a running client will be recorded, which can make debugging a specific issue for a single user much harder.

   Other methods of communicating with the SQL Server, such as ADO (ActiveX Data Objects) which is used by Visual basic for Applications (VBA), are not logged.

2. SQL Profile Tracing – SQL Profile Tracing can be used to log all activity at the SQL Server, including commands from inside Stored Procedures. The default file in which the SQL Profile Trace is stored is named Trace.trc.

   SQL Profile Tracing will capture all activity at the SQL Server for the current user in the system database (typically called DYNAMICS) and the current company database; this means that, unlike SQL Logging, SQL Profile Tracing will record all communication with the SQL Server, including ADO as used by VBA.

   SQL Profile Tracing is not enabled by default, but needs to be configured first; in the next post, I will cover the configuration using recommended settings.

3. Dexterity Script Logging – Dexterity Script Logging tracks all Dexterity event script, procedure and function calls, including the script hierarchy. The default file in which the script log is stored is named Script.log.

4. Dexterity Script Profiling – Dexterity Script Profiling tracks the number of calls to each event script, procedure and function and how much time the calls have taken. It also tracks all table activity initiated by Dexterity and the time taken. The default file in which the script profile is stored is named Profile.txt.

5. Macro Recording – Macro Recording captures all activity performed by the user in the application. this activity is stored in a file called Macro.mac which can be opened in Notepad, which allows for analysis of the users actions and is useful in showing steps which the user didn’t relay when reporting the problem.

   Macro recording will only work foe a single user; in a shared client environment, such as on a terminal or Citrix server, this means the first instance launched.

   Macro recording is only available in the desktop client.

The logging is not provided by GPPT, but is standard functionality which GPPT allows to be easily enabled; without GPPT, enabling them involves several Dex.ini switches.

UPDATE: Winthrop DC have reminded me that the SQL Profile Tracing is functionality provided by GPPT; it is the other four types of logging are standard.

Logging is a functionality which should be used sparingly, as there is a processing “overhead” which can cause speed issues; logging should only be used when investigating a specific issue.

GP Power Tools (GPPT) is split into four modules. The module I am going to cover in this series of posts, is the System Module. This module is included in the licence when any of the other three modules is purchased.

These tools are the ones which provide the basic debugging and support tools:

1. Logging Control including Manual Logging Mode – Manually turn on SQL Logging and Dexterity Logging and Profiling
2. ScreenShot – Capture and either email or save Screenshots and System Status information
3. Send Email – Send Email messages from within the application
4. Dex.ini Settings – Change System and Debugger Dex.ini Settings for the current workstation
5. Configuration Export/Import – Export and Import settings
6. Administrator Password Setup* – Create optional separate password to be used when accessing Advanced mode features
7. Logging Settings* – Change system wide Logging Settings such as shared path location, default logs and SQL Profile Trace setup
8. Email Settings* – Change system wide Email Settings controlling the email engine used by the tool
9. Configuration Maintenance* – Clear GP Power Tools data tables
10. Setup Backup and Restore* – Backup all data in SQL Tables to Debuggger.xml file and restore from Debugger.xml to SQL Tables

Tools listed with an asterisk (*) is an Advanced Mode tool.

This post is a continuation of the Hands On with the GP Power Tools (GPPT) series. I have split it out into a separate series as there may be a large number of posts.

This is the series index for the Hands on with GP Power Tools – System Tools. These are the tools which become available when you purchase any of the other three modules of GPPT.

Continue reading “Hands On With the GP Power Tools – System Module: Series Index”

With GP Power Tools (GPPT) installed and configured, it is now available for use.

Before starting to cover the functionality of GPPT, I thought it might be useful to give a quick oversight of where GPPT is accessible.

Firstly, from an Administrators point of view. Generally administrators will require access to all of the functionality of GPPT. While traditional drop down menus can be used to navigate, they are not the most user friendly method:

Continue reading “Hands On With the GP Power Tools: Navigating the GP Power Tools”

In the last post, I installed GP Power Tools (GPPT); in this post I am going to initialise it in on one client machine (the initialisation will be global on all installations).

The initialisation process requires elevated privileges on SQL Server as the settings are stored centrally in the GP database and GPPT creates its own tables. So to complete the initialisation we need to log in as the sa account, or preferably another account which has been given eleveted privileges:

Once you have logged into a company, GPPT will deploy all of the database objects and create some default settings. These settings include some Security Tasks and Roles. The roles which will be created are:

• GP POWER TOOLS USER grants access to Standard Mode features.
• GP POWER TOOLS ADMIN grants access to all areas of GPPT.
• GP POWER TOOLS PASSWORD grants access to maintain the GPPT System Password.
• GP POWER TOOLS SERVICES is created only in Microsoft Dynamics GP 2015 and later.

Continue reading “Hands On With the GP Power Tools: Initialising the GP Power Tools”

With a licence for GP Power Tools we can now download it. Versions are available for Microsoft Dynamics GP 2010, 2013, 2015 and 2016 so make sure you select the correct version.

Once you’ve downloaded the installer, you need to install GP Power Tools on every machine with the Microsoft Dynamics GP client installed.

Do this, by running the installer and clicking Next on the Welcome step:

Continue reading “Hands On With the GP Power Tools: Installing the GP Power Tools”

In the last post, I covered the tools available in the GP Power Tools. In this post, I’m going to take a quick look at the licencing.

Versions of GP Power Tools are available for Microsoft Dynamics GP 2010, 2013, 2015 and 2016, but the licencing is version independent so you don’t need to worry when upgrading. All you need to do is download and install the correct version.

A licence for GP Power Tools is valid for one year and must be renewed annually; failure to renew will result in the product stopping working. Reminders of expiry will be given in advance as a reminder to renew, but there is also a grace period after expiry. Once purchased, GP Power Tools will install the keys automatically using a web service.

When you want to purchase a licence for GP Power Tools, head to either the Order Now or Get a Quote page. In the Order Software Licenses select from the threee GP Power Tools sets of tools you require. As covered in the last post, there are three modules available:

1. Administrator Tools
2. Developer Tools
3. Database Tools

For testing purposes, GP Power Tools can be installed on an implementation of Microsoft Dynamics GP which only has the sample company deployed; any other company being added does require a licence, but you can request a 30 day trial.

Trials are also available for modules which you have not bought. For example, if you have previously bought the Administrator Tools, you could get a trial licence for the Database Tools.

If you’re a partner and want to do some testing, learning or internal training on the GP Power Tools prior to recommending it to clients, NFR (Not For Resale) keys are available from Mekorma.

Once you have confirmation your order has been placed, you’re ready to download and install GP Power Tools.

Before I move onto the features of the GP Power Tools, there will be a small number of posts, starting with this one, introducing the GP Power Tools and on the installation process.

GP Power Tools is sold as three modules which can be bought separately, with some standard features available when any module is registered. The three modules and their features are:

1. Administrator Tools
2. Developer Tools
3. Database Tools

Essential system features that come with the first module you register:

1. Capture and email 5 system logs in “One-Click”.
2. Capture and email a full system status report and screenshots of all open windows in “One-Click”.
3. Send emails from inside Dynamics GP even with no email client installed.
4. Change Dex.ini and registry settings from inside GP, including making GP work well on high res monitors.

The key features of the Administrator Tools are:

1. Avoid data entry errors! Company based colour schemes provide an immediate visual cue to which company is being used.
2. Gain full administrative and audit control of your security system, including Deny-Based Security.
3. Roll out Dex.ini setting changes to all workstations.
4. Simplify troubleshooting by disabling third party products and customisation (including Visual Studio Addins and VBA).
5. Users can customise window positions and sizes based on the how they use the system.

The key features of the Developer Tools are:

1. Create, execute and publish scripts from inside Dynamics GP, using  Dexterity, Transact-SQL, Visual C# and Visual Basic.Net.
2. Create triggers to schedule events, customise Dynamics GP, and debug issues by automatically capturing logs.
3. Build custom Report Writer functions or custom Service Based Architecture (SBA) service procedures.
4. Request parameters from users for scripts without needing any additional programming.
5. Group triggers, scripts and parameter lists together into development projects for easy maintenance and exporting.

The key features of the Database Tools are:

Synchronise and repair Dynamics GP Companies and Users with SQL Server Databases, Logins and Database Users.

Update Logins and passwords after moving to a new SQL Server or when creating test environments.

Clean up system tables and validate database integrity and table structures before upgrading to minimise upgrade issues.

Export and import selected data from multiple tables using XML for quick transfer of small amounts of data between systems or for backups.

The tools contain two types of features; Standard Mode and Advanced Mode:

1. Standard Mode features can be used safely by all users.
2. Advanced Mode features require system administrator or database owner (dbo) privileges and require expertise in Dexterity, Visual C#, Visual Basic.Net and/or SQL Server administration.

All of my Hands On With posts so far have been with Microsoft Dynamics GP itself, but I am now branching out and going hands on with the GP Power Tools by Winthrop Development Consultants.

GP Power Tools for Microsoft Dynamics GP is a Dexterity, Visual C# and Visual Basic.Net based integrated product for Microsoft Dynamics GP which contains a collection of utilities and tools to make the tasks of administering, supporting and developing Microsoft Dynamics GP easier and faster and is based on the product previously known as the Support Debugging Tool for Microsoft Dynamics GP.

GP Power Tools is distributed by Mekorma.

This series will open with the installation and basic configuration of the GP Power Tools and I will then move on to posts covering the features of the three sections into which the GP Power Tools is separated into:

1. Administrator Tools
2. Developer Tools
3. Database Tools

Each of these sections will have its own series index, with this post being the series index for these sub-series.

Continue reading “Hands On With the GP Power Tools: Series Index”