Click here to
Subscribe to
our Newsletter
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
One great thing about doing the job I do as an Escalation Engineer on the Asia Pacific Microsoft Dynamics GP support team is I have no end of support cases from which to draw ideas for blog posts from.
So here a Dexterity case I helped with recently.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A while back, I posted some articles which used the Support Debugging Tool and non-logging Automatic Debugger Mode triggers to “encrypt” data.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
While I am updating examples, I have made some changes to the Adding Window Size and Position Memory using the Support Debugging Tool sample code.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A little while ago, I posted an example of Obscuring Table Data Fields using the Support Debugging Tool.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A recent post on DynDeveloper.com caught my eye as I have faced a similar problem before and had to work quite hard to get the correct answer.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
My colleague, Allan, had a case recently where the customer had noticed that the Credit Card Number field stored on the Customer Master table at the SQL Server level was not encrypted or obscured and could be seen by anyone who could access the data.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This article is another Support Debugging Tool Non-Logging Trigger example and is a follow up to two previous articles:
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
As a follow on to the article: Using Support Debugging Tool Non-Logging Triggers, I thought I would post a few small examples of how Non-Logging Triggers can be used for simple customizations.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I had a case a couple of weeks back, where the customer wanted to filter the transactions shown on a Receivables Management Statement. There was one type of transaction that they did not want included on the statements sent out to the customers. The transactions to be excluded could be identified by a particular value on the Description field on the transaction.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Have you ever had to develop Dexterity code that needs to read data from a company other than the current Microsoft Dynamics GP company? Well, with my latest updates to the Support Debugging Tool, I came across this requirement.