This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
This will be a 2-for-1 post today as the example given solves a frequently asked question and was used to solve a customer issue.
Triggers
Using SQL DB Update Trigger With Text Fields
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
An ISV had a goal of creating an audit table of the Dynamics record notes table – SY03900 – but was running into an issue.
He mentioned that he was using an “instead of update” SQL trigger and not just a normal “update” trigger. The specific issue was that while his audit table was being updated, the SY03900 table was not.
After discussing the goals of his application and the issue, I set out to discover why exactly the normal update trigger wouldn’t work, why the SY03900 table wasn’t being updated, and lastly what we could do about it.
Limitations of Dexterity Table Triggers
This 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.
Filtering eConnect Requester data
This is a reposting of an article Emily Halvorson originally wrote on my Developing for Dynamics GP blog.
I wanted to tell you about a recent case I had where the Partner was trying to restrict the Microsoft Dynamics GP data they had selected with the eConnect Requester Setup Tool.
They were first importing some of their Sales Orders from an external system into GP with eConnect. Then when they fulfilled and shipped the Order within GP, they used eConnect Outgoing Queue to make the updates available to the external system. Their use of GP also includes manually entered Sales Orders and they did not want the updates to the manually entered Orders to be queued.
Accessing a Table Buffer when it is not passed as a parameter
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:
- Using the Dexterity Three Trigger Technique Part 1
- Using the Dexterity Three Trigger Technique Part 2
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.
Understanding Cross Dictionary Dexterity Development
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?
Using the Dexterity Three Trigger Technique Part 2
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.
Using the Dexterity Three Trigger Technique Part 1
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 …
Working with Unrestricted Database Triggers
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I recently responded on a Newsgroup posting where the developer was wanting to identify a table delete event from a particular form. However, the delete event was happening in a function or procedure that did not pass a form’s table buffer as a parameter and so did not use a form level table buffer belonging to any form. This means that it was not possible to use a form restricted database trigger, but using an un-restricted database trigger was picking up table delete events from multiple forms.
So how can I identify when the database event is being generated from the form I am interested in?
Dex – Working with the Action Button on the SOP_Entry form
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Time to get into some Dexterity code. I saw a posting today on the Microsoft Dynamics GP community forum. It was asking about the disappearance of the Void Button from the SOP_Entry form and how to work with the new Action Button.