With Microsoft Dynamics GP 2015, ignore the old thinking on new releases

There’s been a lot of interest lately in Microsoft Dynamics GP 2015, but I’ve heard from a number of people that their company won’t move to the latest release. They insist on waiting until the first service pack or implementing one version back.

The world of software is changing in ways that make that thinking outdated and, in a cloud focused world, impossible to adhere to. But lets talk about GP 2015 specifically.

As I look at and work with GP 2015, I don't think of it as a major release. To me, GP 2013 R2 was the major release and 2015 is really the first update. The naming sequence was marketing-driven and here is why:


Requires FREE Membership to View

Become a Member Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Mark Polino

Mark Polino is a Microsoft MVP for Dynamics GP and the Director of Client Services for Fastpath. He is author or coauthor of five books on Microsoft Dynamics GP. Mark has been working with Dynamics GP and its predecessors since 1999. He is a Florida licensed CPA and holds an MBA from Rollins College.

Building Dashboards with Microsoft Dynamics GP 2013 and Excel 2013Mark's new book, Building Dashboards with Microsoft Dynamics GP 2013 and Excel 2013, is available now.





Read full bio...

I've been telling clients

I've been telling clients since GP 2015 came out that the old approach to deployments was dead; a number of them are now planning to upgrade to 2015 in the very near future.

Ian Grieve

Not sure I agree

I am not sure I agree with this 100%. There are a number of ISV products still not ready for GP 2015. There are also things that got broken - like PSTL - with the GP 2015 release. I think waiting until at least the first service pack still makes sense. With the changed support lifecycle, it also does not make sense to rush into upgrading, even if you consider this more of a service pack.


Not sure I agree either...

My upgrade project is now waiting for the March Hotfix.

Tim Foster

To bleed or not to bleed

There is merit in staying on that cutting edge, but there is risk in doing so. Being on the customer side and partner side, I always want my users to get the most benefit that is coming out in the product. I am happy that MS is pushing updates like this.

It is hard for ISVs to keep up and test their product. For customers that are just using core product, upgrading right away may be ok. For others, and like myself with very large GP databases, we wait about 1 quarter before we start testing and deploy. This helps mitigate our risk, identify any bugs, and allows our ISV partners to be better prepared.


Trust and Verify...

We were just having this conversation in house today. I think fundamentally your argument doesn't address the most difficult question: "Will the new release be bug free?" Since experience would tell us NO- then an upgrade, on premise or hosted requires testing with your 3rd parties and your data. When we went to GP2013 R2 with 30 end users, most GP modules and 1/2 dozen major 3rd parties it took us a solid 2 months of work. Does the normal team just trust Microsoft and not test it? What do they tell their auditor? This makes no sense on an annual basis.

Trust and Verify, but risk staying behind


I read your reply with interest.

I convinced myself a long time ago that software is written by humans and will never be bug free - no exceptions. Ever since, I manage to sleep better at nights :) My customers are also getting the message.

Our discussions with our customers are now focused on updating their Microsoft Dynamics GP system on a regular basis - no different than applying a service pack - and rather have moved away from the long, tedious, and time consuming planning of annual or even 2-year upgrade cycles.

A leap of faith? Maybe, but I don't see what auditors and service packs have in common. I will agree wholeheartedly that GP 2013 - not GP 2013 R2 - was a major step up from GP 2010, but subsequent updates since have been a breeze. In fact, I just updated our company from GP 2013 R2 to GP 2015 in less than it took to finish my lunch and this included 3 company databases and the system database, plus recreating our demo environment (ah, the beauty of Azure!)

As for your comment on ISVs (third party products), I think most have now caught up - the major transition being GP 2013 which saw the release of the web client and major architectural changes. Keep in mind that ISV products were compatible 100% with the desktop client - by the way, so were all Microsoft Dexterity-based Add-Ons) and gradually they made changes in their product for full compatibility with web client, mostly around code optimization (hence the release of HR, MFG, and FSS compatibility with web client for GP 2013 R2).

Like with all major changes, some folks just didn't make the transition and did not want to adapt to the changes, but that's true for any technology. As a result, some ISV products are still only compatible with the desktop client, but not so with the web client.

As a partner, we have learned to embrace and trust the process and it's paying off. Our customers for the most part are all on GP 2015 and have experimented little to no pain in the process of getting there. More importantly, we now have the time to talk to them about other technologies such as Azure and embrace of Web Client without losing sight of their on premise deployments.

Mariano Gomez, MVP
Intelligent Partnerships, LLC.