Microsoft Dynamics GP Roadmap Update

Back in April I published an article describing Microsoft Dynamics GP roadmap up to release GP 11 Future Pack. The timeline also described what would happen at least up to 2011.

Just recently the Microsoft Dynamics GP Product Management and Marketing team released a new stub titled Microsoft Dynamics GP "11" Preview with a link to the Dynamics GP "11" Presentation Pack (visit their site for more info). The presentation pack contained a Microsoft Office PowerPoint presentation describing the Dynamics GP roadmap up to GP "14".



To comment a bit on the roadmap, the Product team has a vision that extends beyond the initial 2011 scope delivered back in April, throughout to 2016, which quiets down rumors as to the future of Dynamics GP and reafirming Microsoft's real commitment. While the bullet points accompanying GP "12" and GP "14" are pretty vague, it's worth mentioning that GP "14" is contemplating a major user interface update. I won't be surprised to see more improvements to the GP ribbon and perhaps even extensibility of forms and reports with Visual Studio Tools for Applications. What is Visual Studio Tools for Applications? It's Microsoft's replacement for VBA. After all, VBA is old technology --reminiscence of Visual Basic 6 -- and served it's purpose already if you ask me.

What else to expect? Integration, integration, integration... tighter integration with Microsoft Office, tighter integration with Microsoft SharePoint Server, bigger-broader enhancements to BI, and even support for cloud computing deployments with SQL Azure.

Keep in mind as you read this article that these comments are my personal point of view based on the trends I am seeing across all Microsoft product stacks and do not represent the views and/or directions of Microsoft.

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more