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

A couple of weeks ago, I had another interesting situation raised by Sivakumar Venkataraman.  In this scenario, we had a custom Dexterity dictionary installed on a customer’s system. This customisation contained a table definition for a temporary table. To support some additional functionality, the temporary table needed an extra index added.  Installing the updated chunk on the customer’s system failed to add the new index to the table definition. Running the code generated errors about an invalid index.

Read more →

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

Here are a couple of really cool tricks that can boost performance of your Dexterity code for almost no effort at all.  The techniques discussed below can significantly speed up accessing table buffers in functions and procedures when looping through a range of records in a table.

Read more →

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

“Why doesn’t my Dexterity table trigger fire when the table is changed.”

I have heard this question asked a number of times and so I thought I would highlight some of the possible reasons for the trigger failing to fire.  Some of the reasons can be resolved by coding, while other reasons are a limitation in the way Dexterity table triggers work and cannot be resolved from inside Dexterity.

Read more →

David Meego - Click for blog homepageThis 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.

Read more →

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

Most Dexterity developers would have seen the pragma(disable warning LiteralStringUsed) command used at some stage to avoid literal string warnings when hard coded strings are needed as part of a script. This can often be the case when building SQL where clauses or pass through SQL, sanScript or macro code.

Read more →

Dave Dusek - Click for blog homepageThis is a reposting of an article Dave Dusek originally wrote on my Developing for Dynamics GP blog.

This particular situation has come up in a number of support incidents and I also run into this myself on occasion.  The situation is that you have a cross dictionary procedure or function trigger on a script and one of the parameters is a third party table buffer.

Read more →