Tag: support debugging tool
Following on from my previous post: Customising the Company Login window series Part 1 – Introduction , here is the method to create a solution using Visual Basic for Applications (VBA). As discussed in the earlier post, the problem we are trying to overcome is that the company drop down list on the Company Login window is not wide enough to show a long company name.
Wow – time flies and as they say, it seems to go faster the older you get. It seems only a few years ago that I was a graduating senior at NDSU. It was late in the last week of finals and I was working with my team to finish my senior project for one of my engineering classes before graduating (with a BS in Electrical Engineering with Computer option)
I am back from my leave this week and have been working through my backlog of emails and other tasks.
The Inside Microsoft Dynamics GP blog continues with the Microsoft Dynamics GP 2013 R2 Feature of the Day (FOTD) series. Here are the previous features: Microsoft Dynamics GP 2013 R2 Feature of the Day Week 1 Microsoft Dynamics GP 2013 R2 Feature of the Day Week 2 Microsoft Dynamics GP 2013 R2 Feature of the Day Week 3 Have a look at the posts from Pam Misialek for week 4: Microsoft Dynamics GP 2013 R2 Feature of the Day: Azure Backups Microsoft Dynamics GP 2013 R2 Feature of the Day: Suggested Items Enhancements Microsoft Dynamics GP 2013 R2 Feature of the Day: Suggested Items Part 2 Microsoft Dynamics GP 2013 R2 Feature of the Day: Dashboards To see all the Feature of the Day posts use the link for the Feature of the Day tag . Enjoy David
Almost 18 month’s ago in December 2012, Microsoft Dynamics GP 2013 was released, now I am pleased to announce the release of Microsoft Dynamics GP 2013 R2. Yes, that’s correct, Microsoft Dynamics GP 2013 R2 is now available for download from PartnerSource and CustomerSource
Hi everyone, my name is Kevin Racer and I’m a Senior Program Manager Lead on the Dynamics GP team. I spend my days working on improving our architecture and tools. Overview A good number of you have probably seen or heard about the change to our architecture designed to better embrace services and the cloud. We’ve officially referred to it as our Service Based Architecture code named “DexNext”. This change is scheduled for the Microsoft Dynamics GP 2015 release around Q4 2014 and has a number of pieces that developers, partners and customers need to be aware of if they want to take full advantage of these new and exciting capabilities. In this article I am going to broadly describe the architecture as its technologies and then in subsequent blogs the team will follow up with deeper dives on the specific components. Let’s start with what Service Based Architecture means. If you think of the term service oriented architecture (SOA) then you are on the right track because that’s what the new architecture essentially models. We call it service “based” because it more accurately describes what we are doing. Any functionality in any dictionary can be exposed as a service call, which makes it the “base” for the services as well as the base for web and desktop clients. Our aim with this was consistent with what we did with the web client in that we are evolving our architecture by adding technological capability while continuing to leverage existing resources. Technologically speaking the architecture lets developers precisely control what gets exposed through the endpoint and includes the ability to define in .NET the makeup of the data you want to exchange. While .NET is an added factor, the experience is still primarily a sanScript one so for those of you with that skillset it continues to have value. The endpoint API conforms to a REST based pattern which is very simple to understand yet allows the invocation of some very complex operations. We will also provide a Discovery Endpoint that describes all available service calls in a particular deployment. This description includes things like parameter type requirements, a description of the method and an example URI to call it. You can think of Discovery as real time documentation that is always current.