This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
My good friend, Mariano Gomez (The Dynamics GP Blogster) raised this issue recently. He wanted to use the method I discussed in my previous Quick Tip post: Quick Tip: Accessing Third Party Table Buffers using anonymous tables to gain access to the third party table so he could display it in a Scrolling Window on his form.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I have been spending a lot of time recently working on consulting engagement in Malaysia. This project involves a large amount of custom Dexterity code, some of which involves accessing tables in other third party product’s dictionaries.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
As you may know, I was one of the pioneers of Cross Dictionary Dexterity Development and have posted about it a number of times (also see Can I customise a 3rd party form with Dexterity? and Understanding Cross Dictionary Dexterity Development).
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is the second in a series of posts which are are designed to help Dexterity developers as well as VBA and Visual Studio Developers to understand how to work with passthrough Dexterity sanScript. The main focus of this series is to understand how to change the Dictionary Context that the code executes in.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is the first in a series of posts which are are designed to help Dexterity developers as well as VBA and Visual Studio Developers to understand how to work with passthrough Dexterity sanScript. The main focus of this series is to understand how to change the Dictionary Context that the code executes in.
This is a reposting of an article Dave Dusek originally wrote on my Developing for Dynamics GP blog.
Recently, I have been getting a lot of customization requests for Safepay, specifically, adding information into the detail line in the safepay file. Safepay customizations like that are pretty much all the same thing, no matter what field you want to add, so I figured I would share my integration point and how to handle these types of customizations. I have done probably 4 or 5 of these in the last couple of months.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This post is a follow up to the previous posts on the Three Trigger Technique. If you have not read the posts explaining this technique, please use the links below:
The idea of the three trigger technique is to use a trigger on an unrelated function or procedure call to get the timing you require for your code. The 1st and 2nd triggers are used to ensure that the 3rd trigger is only used when it is called from your desired parent script.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A recent newsgroup post has raised the question of whether it is possible to customise an alternate form using Dexterity. This is covered on my earlier blog post: Can I customise a 3rd party form with Dexterity?
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
In the previous part of this post we discussed the theory of the Three Trigger Technique and the details of a problem that was solved using this technique.
This post will cover the actual solution used and has the scripts used so you can see the techniques in action.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
When working with Dexterity triggers, the hardest part of the process is working out where to place the triggers. There are times where it seems impossible to get the trigger you need in the correct location. This post explains the concept of what I call the Three Trigger Technique. The technique involves using a trigger on an apparently unrelated function or procedure which executes at the appropriate point within the code of the function or procedure. Let me explain in more detail …
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
One of the great things about Dexterity is that you can develop complex customisations without needing access to the source code. Even if you have access to source code via the Source Code program, a Dexterity developer never actually changes original source code.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Over the last few weeks I have been asked a number of times about methods of customising a 3rd party form. This purpose of this post is to clarify what can and cannot be achieved with Dexterity.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
When I started this blog, one of my goals was to help developers push the boundaries of what they believe is possible. This was the foundation of the materials presented at conferences by myself and Mark Rockwell. For more information on the conference sessions and materials have a look at the Cross Dictionary Dexterity Development post.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Back 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.
Winthrop Development Consultants Blog 