Friday, October 17, 2014 Ok, what just happened last night, ugh! Day 2 was quite the day (and the night!). However, the Summit was coming to an end and it was almost time to close the curtains on what I personally reckon to be a very successful event. This meant participating in the last networking huddle event, which had tables organized by roles; visit the Expo one last time to say bye to ISVs who tirelessly worked to bring some of the best products to market; and attend maybe a session or two going throughout the day
Technorati Tags: gp 2013 , upgrade , cursor error Recently I did an upgrade from GP2010 to GP 2013 R2 (build 1745) and ran into a variety of problems.
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.
Thanks to my good friend David Musgrave over at Developing for Dynamics GP for nominating me to the ALS #IceBucketChallenge . David was originally nominated by MVP Jivtesh Singh . See his blog post and video here: David completed his challenge (and donation yesterday) and posted this article on his blog as proof of his accomplishment.
When executing Dynamics Utilities for a brand new installation of Microsoft Dynamics GP 2013 R2 you may have noticed a new window in the guiding wizard. This window is the Web Client SQL Server Login window, which allows you to specify a common SQL account that will be created during the system database setup process