Development Matters Blog

As the knowledge of Dexterity and Microsoft Dynamics GP grows, the projects get bigger and more complicated. The customizations we produce are more and more tightly integrated with core Dynamics GP processes and very often they control and change those core processes and flows.

Such modifications are quite challenging for developers and they most often like to deal with such problems. The main pain point that rises from such customizations are bugs or issues which might appear due to the uniqueness of a customer’s environment or data. Such issues are very difficult to replicate which leads to very ineffective support.

Asking customers to enable the Script Debugger and create a log file or organizing Live Meetings with a demonstration of the issue can often be time consuming for both sides. The elegant solution for such cases may be creation of log files directly from our code. The Developer can incorporate the creation of log files directly in the code which calls the “risky” logic through ScriptLog_Start() and ScriptLog_End() functions of Dexterity.

Logging will overwrite the previous log file every time “risky” logic is initiated. In most cases the issue is identified immediately so if path where the log file is saved is documented, the customer can attach it to a support request and make identifying of the cause much easier.