From the GP Blogs: Using SQL Triggers; How to Perform Year-End Closings; Running Microsoft Office 2010

Proceed with Caution: Using SQL Triggers with Dynamics GP: Dynamics GP Land walks us through an actual example in which they chose to use triggers: "SQL database triggers are an interesting, powerful, and potentially dangerous tool. On the one hand, they offer the appealing ability to execute an SQL script automatically, whenever a change is made to a database table... On the other hand, triggers can be difficult to implement, debug, and manage, and can cause unintended consequences."

"I was recently asked to customize GP to automatically populate a single field on a SOP transaction... After weighing the pros and cons of different approaches, I chose to use triggers. I reasoned that triggers would be the most reliable, as they could most easily populate the field regardless of how the order was entered in GP, and a trigger could be fired without requiring any user intervention... I think that triggers turned out to be a good choice, but I ran into a few surprising issues that required me to learn a few things about GP, and also how to debug triggers on SQL Server..."

Microsoft Office 2010 and Dynamics GP10: The Dynamics GP Blogster installs Microsoft Office 2010 Professional and tests the traditional Dynamics GP operations with SmartLists and Navigation Lists: "I have to say I am pretty impressed... The installation process went pretty smooth and I was surprised to see all my Microsoft Office 2007 components upgrade without ...