What a week of learning that reIMAGINE 2014 conference was! If you stayed for the post conference training classes, even more power to you. In my previous article (see Microsoft Dynamics GP 2015 Developer’s Preview: .NET Framework Interoperability – Part 3 ), I talked about the .NET interop capabilities introduced in this iteration of Dexterity and how these new capabilities have become the foundation for unlimited extensibility options for Dexterity-based applications. Today, I wanted to talk about another aspect brought by .NET interop: Dexterity services. However, to understand Dexterity services, we must first take a look at the service implementation patterns
November 10, 2014 After my pleasant trip to Fargo on the previous day , it was time to check in and complete the registration process with the lovely ladies from Dynamic Communities . It helps to have a reputation in the community as my badge was handed to me without showing an ID
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.