Customer, Partner Needs Will Influence Microsoft Dynamics GP Release Cadence in 2017 and Beyond

June 8 2016

Snare Drum 

The Microsoft Dynamics GP team will continue on its two release per year cadence through 2016. But, the GP team has advised, customer, VAR, and ISV feedback could potentially change that plan in the future.

About Jason Gumpert

As the editor of, Jason oversees all editorial content on the site and at our events, as well as providing site management and strategy. He can be reached at

Prior to co-founding, Jason was a Principal Software Consultant at Parametric Technology Corporation (PTC), where he implemented solutions, trained customers, managed software development, and spent some time in the pre-sales engineering organization. He has also held consulting positions at CSC Consulting and Monitor Group.

More about Jason Gumpert


gtho's picture

I always try to upgrade to the latest release because MS has stopped releasing fixes to the old releases. For example, Field Service has at least 3 critical bugs in GP2013-GP2015 R2 and they didn't get fixed till version 2016 or at least were not scheduled to be fixed. I think MS needs to concentrate on fixing outstanding bugs instead of releasing new features which in many cases can't be used such as pre-payments on POs, try using that if you have an integration that uses econnect, you can't. Businesses such as the one I work for lose money and look like fools when they can't even quote out of Field Service because it affects backordered qtys and Bin level allocations. Why should we spend thousands constantly upgrading just to get a fix? I can understand upgrading to get a new feature but not for getting things fixed. Rant over, Arthur