In my previous post I talked about all the out of the box options for setting up Integration Manager (“IM”) logs and frankly, the Trace level log is good for most users of IM users. However, when “good” is not good enough, it’s necessary to resort to some of the objects and functions available as part of IM’s scripting library.
This week’s Tech Tuesday article is from our Support Guru, David Youngquist, who will walk you through how to perform a SQL trace to debug eConnect errors. 1. Find out what user the eConnect service is running under
Last week, I had an interesting case where a Dexterity Developer was having trouble getting some code to update a range of records selected in a table. The code would only update the first record in the range
Hello! I just want to first take a second to introduce myself since this is my first post on the Developing for Dynamics GP blog. My name is Lucas Miller and I’ve been supporting Microsoft Dynamics GP since 2005. Like much of the team I’m based out of Fargo, ND, USA. I’ve been married for almost 2 years and my wife and I are expecting our first in just under 3 weeks as of this writing. My main focus has been on the system side, but the last couple years I’ve been focusing on import tools (e.g.