Developing for Dynamics GP

by David Musgrave (Perth, Australia) and Microsoft Dynamics GP Developer Support Team (Fargo, ND, USA)

Cross Dictionary Dexterity Development

Cross Dictionary Dexterity Development

  • Comments 23

David MeegoBack in 1998, when I was working with Sequel Technology (the Western Australian partner for Great Plains), we were implementing Great Plains Dynamics 4.0 for a couple of sites and were using add-on products for Service Management and Job Costing.

My business partner at the time (who did the sales) understood that Dexterity applications could be easily customised and so promised some changes to the customer.  What he (and I) did not understand at the time were the limitations Dexterity has for working across dictionaries. 

We did have some "with name" commands which could open forms, call procedures and run reports. We also had the execute() function which could be used to run Dexterity sanScript in the context of the 3rd party dictionary.  What we did not have was cross dictionary triggers.

Based on putting a number of ideas together I came up with a method of hacking the 3rd party extracted dictionary to add global procedure containing a call with name in dictionary command. This was a redirector stub procedure to work as a trigger handler script to call back into my dictionary where the real trigger handler code was located.  Then I could use execute() to register the trigger in the context of the other dictionary and use the hacked handler script to eventually call back into my code.  Luckily, once cross dictionary triggers were added into Dexterity 5.10, there was no longer a need to hack a 3rd party dictionary (which is not really allowed). Thanks to Dave Gaboury and Andrew Ingalls in Fargo for working with me to create proper cross dictionary triggers.

Anyhow, I was given the opportunity to present a session on this hack method (for v4.0 and v5.0) as well as other cross dictionary techniques at the 1998 Great Plains World Wide Developer Conference in Fargo.  This session was called Integrating with Third Party Dictionaries and was a hit with the development community. Later when I was with Winthrop Dexterity Consultants, I was able to present an updated version of this session using cross dictionary triggers (for v5.5 and v6.0... and later) at the Summer Tech 2000 Conference.

In 2001, I worked with Mark Rockwell from Rockton Software and created a new session called Pushing the Limits with Dexterity. In this session we discussed how to write code that was multi-dictionary friendly and showed how to create a Resource Explorer window as well as other techniques we are worked out.  Sadly, I was unable to get to the Summer Tech 2001 conference and so Mark presented it by himself.  An updated version was presented by both of us at the Tech 2002 conference in Fargo.

While the materials are a little bit old, the methods and concepts contained in them are still valid today and are the basis for the best practices of cross dictionary Dexterity development. These materials are available for download from both the Winthrop and Rockton websites and now also from this blog.

Note: There is a section in the "Integrating" conference materials on Modifying 3rd party forms. The method discussed is not recommended as it breaches the Dexterity License agreement (not allowed to ship a modified application dictionary) and also causes problems when applying upgrades and service packs.  The later "Pushing" materials contain a Warning about modifiying 3rd party forms to explain some of the issues. For more information have a look at the following post: Can I customise a 3rd party form with Dexterity?

An archive containing the latest versions of both conference sessions is attached at the bottom of the article.


Please add your comments to say how you have used these materials. 


02-May-2010: Cross Dictionary Triggers against the Dex.dic (dictionary 1) do work now.  I am not sure what version that was changed on, but it is possible to use execute() AND triggers on the runtime engine Dexterity based components. Thanks Elmo for this info.

24-Nov-2010: Updated post to highlight that direct modification of a 3rd party form is against the Dexterity license agreement and is not recommended.

Attachment: Integrating with 3rd Party Dictionaries & Pushing the Limits with
  • David,

    I could not help after reading your article to go back to my blog and write about my experiences around the 3 conferences you presented -- Integrating, Pushing I, and Pushing II, as they have become known.

    The fact remains, these techniques became the cornerstone of Dexterity programming and are now used worldwide by thousands of ISVs. You have always been someone we look up to when all options have been tried without any luck. Keep up the good work!

    30' commercial: stop at my blog and read my accounts from those days... the good o' days!


    Mariano Gomez, MVP

  • Posting from Dynamics GP Blogster

  • When I started this blog, one of my goals was to help developers push the boundaries of what they believe

  • Over the last few weeks I have been asked a number of times about methods of customising a 3rd party

  • One of the great things about Dexterity is that you can develop complex customisations without needing

  • Recently I responded to a question on a newsgroup asking how to minimise a window from VBA (Visual Basic

  • Recently I responded to a question on a newsgroup asking how to minimise a window from VBA (Visual Basic

  • When working with Dexterity triggers, the hardest part of the process is working out where to place the

  • In the previous part of this post we discussed the theory of the Three Trigger Technique and the details

  • David, I need to go further with integrations. How can I open a lookup with data from another company (database), for an existing table definition? For example, I'm logged in Company 'A', but I need to open an Item lookup with items from Company 'B'

  • Hi Marcos

    This is not quite cross dictionary, but it is something unusual.

    I think that you will need to use a FORM_PRE trigger on the lookup form to close the table and re-open it with the open table as command and specify the database type and pathname.  You can get the pathname by reading the SY_Pathnames table for the company and series.

    Once you have changed the table being used the lookup should work fine.... off the other company.

    You will also need to check that user has access to the company using the SY_User_Company_Access_REL table.


  • David, thanks for your advice. As always, it was very useful.


    PS: How can I do to become a member of the 'Musgravion' Circle?

  • Hi Marcos

    You are reading the blog. So you must already be a member. :-)


  • This particular situation has come up in a number of support incidents and I also run into this myself

  • This particular situation has come up in a number of support incidents and I also run into this myself

Page 1 of 2 (23 items) 12
Comments Information


Please only post comments relating to the topic of this page.

If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.

Leave a Comment
  • Please add 6 and 1 and type the answer here:
  • Post