Dex – Identifying the build number of a Development Dictionary

David Meego - Click for blog homepageThis is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.

In a recent post on the new Partner Forum, it was asked how to identify the build number and hence Service Pack/Hotfix number of a Dynamics.dic dictionary being used as a development dictionary for writing a Dexterity customization.

So, here are four possible methods you could use:

A: To check the build of a development dictionary from inside Dexterity.

From the Resource Explorer window:

  1. Click Application.
  2. Double click Install.
  3. Locate Module 066 and read the Build Number.

B: You can also go into Test Mode (Debug >> Test Mode) and the version is displayed on the bottom left corner of the User Login window. Use Ctrl-T to exit Test Mode.

C: From Test Mode (Debug >> Test Mode), If you log in, you can click Help >> About to open the About window and see the version number. Note that logging in with an incorrect build could update version tracking data in the system.

D: Since Version 9.0, you can locate the dictionary file with Windows Explorer, right click on it and select Properties.  Then click on the Dictionary tab to see the version information.  Mariano Gomez mentions this method in his Retrieving dictionary build numbers outside of Dynamics GP post.

For example, my system has the build number 10.00.1193, which is v10.0 Service Pack 3.


This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on

One thought on “Dex – Identifying the build number of a Development Dictionary

Please post feedback or comments

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.