If you haven’t spent much time looking at this dialog in Microsoft Dynamics NAV 2009, then likely you really need to read on:
In the Olden Days
Navision had a pretty standard release world. X.YY releases (such as 2.60, or 3.10) would be the big releases. You’d download a new set of application files and have to do the big merge to get all the customizations and the new objects to play nice. Between big releases, if you ran into a problem that required a hotfix, either for objects or for the application, you’d contact the Support Desk. Support would then send you either the application changes or the object changes. Typically, it was mainly object changes.
– The RTC Era
With 2009, things got a little crazier. Plenty of people have talked about how 2009 has:
- 2009 release
- 2009 SP1
- 2009 R2
And yet, those are all some 6.0.xxxxx version. Microsoft Dynamics NAV 2013 is in the world, and we never moved beyond 6.0 in almost four years!
There’s also a big shift in how application hotfixes are handled. Instead of one-off fixes, Microsoft has a rolling build system. If they fix an issue in build 6.0.32012, the hotfix will be build 6.0.32013 (often build numbers jump up a few versions, however).
This means if you apply an application hotfix that is version 6.0.33210, you’ll have every application hotfix since 6.0.32012 (release R2) included.
Let this fact soak in: As of this writing, there have been 77 hotfixes (each with 1-20 bugs serious enough to call for a hotfix) released since the DVD of Microsoft Dynamics NAV 2009 R2 released 21 months ago.
If you are upgrading or implementing clients at this point, October 2012, and you’re not using a build higher than 6.0.32012, then you might need to rethink your implementation strategy.
To be continued in a post on the challenges of being a partner/developer in the RTC Era with build mismatches.