Time for one of those obscure issue blogs, that won’t affect very many people, but the odd person might find this very useful to clarify what they are or are not seeing happen (and give me a couple of years, I’ll forget, and find my blog post!).

This story starts at a client, who requested that the Transaction Description prints on a cheque/EFT remittance. Sounds easy right? Well, the client found out at some point when first using GP that any descriptions in POP transactions they typed in were not updating PM tables, therefore no descriptions for the reviewers or vendors. So, they called their VAR for help.

Cue the VAR, who at some point early in their original implementation with Dynamics GP 2010, added an Extender window on the Invoice Match Entry window, for A/P Clerks to type in a transaction description, and a SQL trigger on the POP30300 table, to update the PM20000 table with that description after posting completes. Last year, during an upgrade to Dynamics GP 2013, I was new to this client and the issue came up during testing because (of course) the trigger wasn’t upgraded/replaces after the upgrade, no one knew it existed, and the descriptions stopped populating PM tables again.

When the client noticed the problem, I made a note to look into this in the future. First of all, they didn’t need an Extender window when there is an out of the box Reference field in all the POP transaction windows! Second of all, why should we be using a trigger on something so basic? It warranted looking into further to see why this was needed in the first place. (I understand the end goal of the description pushing down to payables but the smelled like something that should just occur out of the box, no trigger, no add-on windows…)