Book Image

Microsoft Dynamics GP 2010 Implementation

By : Victoria Yudin
Book Image

Microsoft Dynamics GP 2010 Implementation

By: Victoria Yudin

Overview of this book

Microsoft Dynamics GP 2010 is a sophisticated Enterprise Resource Planning application with a multitude of features and options. The implementation of Dynamics GP is usually considered to be complex, and can be very confusing for users and consultants. This step-by-step guide will show you how to effectively implement Dynamics GP 2010 with ease.This focused, step-by-step tutorial covers the basics of Microsoft Dynamics GP, from licensing, to design, before moving on to more complex topics such as implementation and setup. You will learn how to install and configure Microsoft Dynamics GP 2010 from start to finish.This book will enable you to master the implementation of Microsoft Dynamics 2010 effectively. This book starts with how to plan and complete a successful Microsoft Dynamics GP 2010 implementation. You will then move on to learning who should be on the implementation team, what important questions should be asked and how to plan your infrastructure for Dynamics GP 2010. Detailed descriptions of all the setup options for the core Dynamics GP modules as well as practical advice on setup will help guide you through the myriad of options available in this powerful application. As you reach the end of the book you will learn how to import your initial data with illustrations and practical examples.
Table of Contents (18 chapters)
Microsoft Dynamics GP 2010 Implementation
About the Author
About the Reviewer
General Ledger Account Categories
Microsoft Professional Services: Additional Tools Available

Dexterity and product dictionaries

Microsoft Dynamics GP is written in a proprietary application development environment called Dexterity. Over the years there have been many questions raised about when Dynamics GP will be rewritten in a different language. There was even an announcement about 10 years ago that Dynamics GP 7.0 would be rewritten in C#. The reality is that Dexterity is here to stay. While implementing Dynamics GP does not require any in-depth knowledge of Dexterity, it is important to understand the terminology and structure of the Dexterity environment.

Dexterity components

Dexterity is a 32-bit environment, with a number of components that work together:

  • Application Dictionaries are files with the extension of .dic that store code and resources. Resources are objects such as tables, windows, and reports.

  • The Runtime Engine combines and interprets code and resources in application dictionaries to result in a functioning user application.

  • The Dexterity Dictionary, Dex.dic, includes resources used by the runtime engine to translate the application dictionaries.

Dynamics GP products

In any installation of Dynamics GP you will find multiple products. Products can be installed and used independently even though they may integrate with other products. Typically each Dynamics GP module will be a separate product. The major exception to this is the Microsoft Dynamics GP product, which includes most of the core Dynamics GP modules.

Each product has the following unique characteristics and components:



Product name

Microsoft Dynamics GP

Product number


Product dictionary


Forms (or Windows) dictionary


Reports dictionary


A Window in Dexterity is an actual screen used in the application to enter or view data. A Form is a combination of windows, menus, and other resources that work together. For example, the About Microsoft Dynamics GP form shown has two windows: About Microsoft Dynamics GP and Microsoft Dynamics GP Options. Together these two windows make up the About Microsoft Dynamics GP form.

The product dictionary contains all the core forms and reports for each product. When the Dynamics GP application is launched, if either the forms or reports dictionary for a product is not found, that dictionary will be recreated from the resources in the product dictionary. If the forms or reports dictionary is found, the Dynamics GP application will look to them first for any windows, reports, code, or resources. This allows any modifications made to windows and reports to supersede the out-of-the-box code, while keeping the original product dictionary intact.

In a typical Dynamics GP installation, the product dictionary is installed locally on each workstation. The forms and reports dictionaries can be installed either locally on each workstation or located on a network share, accessible by all workstations. For implementations with no modifications to the out-of-the-box windows or reports, it is recommended to install all the dictionary files locally for improved performance.

Report Writer and Modifier

Report Writer and Modifier are tools that allow reports and windows in Dynamics GP to be modified.

Report Writer is a Dexterity reporting tool that is included with the Dynamics GP System Manager. With Report Writer, you can modify existing reports or create new custom reports. In a standard Dynamics GP installation there are over 800 Report Writer reports. Typical modifications to reports include adding a company logo, changing the alignment of reports to fit a preprinted form (for example for payables checks), and removing or adding columns on reports. Modified reports for the Microsoft Dynamics GP product are stored in the Reports.dic file.

Modifier is a Dexterity tool for customizing the appearance and behavior of Dynamics GP windows. Modifier is not included in any core Dynamics GP licensing and is available for purchase separately with all of the Dynamics licensing options except Business Ready Business Essentials. Typical modifications to windows include making fields required, hiding fields, changing the name of fields, and changing the tab order of fields. Modified windows for the Microsoft Dynamics GP product are stored in the Forms.dic file.