Finally released in October 2008, the first three tier architecture release with the new RoleTailored Client. The version which we first expected to be in version 5, then 5.1 ended up being the first Navision version with a year as the version. Something we also saw in 2007 when Microsoft Dynamics Entrepreneur Solutions 2008 had been released. And something Microsoft also did with most other systems, like Office 2007. Internally the version is still numbered as version "6.0".
The new version was a hybrid. We both had the old client, which now is called the Classic Client] and the new RoleTailored Client (RTC client]. It offered "One Solution", but "Two Environments". Customers could choose to stick with the old classic, or fully upgrade to the new or have a mixed setup.
The new client also came with a new report designer. Reports were first designed using the old report designer in C/SIDE, as the "native" format was still NAV's. When the basic (data) design was done, the an RDLC Layout needed to be created. Although 2009 offered a function to "Create Layout Suggestion", then it only gave a very basic report and not real layout.
Creating document reports were even harder. And upgrading reports could easily take much more time than just creating reports again. RDLC reports became the most hated about the new version.
NAV 2009 allowed you to run "classic" reports directly from RTC.
The new client required a new object, a Page Object for user presentations. The new page object was XML based and besides being the presentation layer for the clients, then it could also be exposed as a Web Service.
To handle upgrade of Form Objects a Page Transformation tool could convert a form text file to a page text file. As long as you didn't use anything "fancy" in the form. But a simple form like a card or a list, without subpages etc., worked fine. Anything else required you to "fine-tune" the transformation tool.
Version 2009 now also supported web services for connections to NAV. It allowed to expose both codeunits and pages as web services.
As easy as Navision had always been to change, as difficult it had always been to upgrade. Now it was no longer enough to merge code. To upgrade a customized solution both required changed forms to be transformed into pages and classic reports required new RDLC layouts.
The goodbye to forms is not all bad. One of the issues with the old forms, was its source code structured. An exact placement of the field in the form as opposed to the relational placement of the field in a page, made source code compares very unreliable.
With the Powershell upgrade tools in version 2013, and even more so with Extensions in NAV 2016 and later versions, then Microsoft shows that the know they had to do something. But that doesn't help the many customers, who remains in the classic versions for that reason. An upgrade of a customized solution may easily end up being as expensive as a full re-implemenation.
Besides a lot of bug fixes for NAV 2009, then they also release a lot of new functionality. Control Add-in's can now be used in pages. The page desginer also get a new page wizard, categories for promoted actions, field styling and the ability to run pages with the Run button.
Before 2009, users were created only in the Microsoft Dynamics NAV database. In 2009 SP1, creating a new user in Microsoft Dynamics NAV automatically creates corresponding SQL Server users in both the Microsoft Dynamics NAV database and the master database. This change requires Microsoft Dynamics NAV administrators to have greater permissions on SQL Server than for previous versions.
Also, administrators are no longer required to set trace-flag 4616 on SQL Server.
Microsoft released Dynamics NAV 2009 R2 in October 2010. Again a lot of updates as well as new functionality and features.
In the new features the long awaited integration to Dynamics CRM was finally there, something a lot of partners and clients had requested for years. It was not a ready-to-install out-of-the-box integration. It was more a "tool", which allowed us to build these NAV to CRM integration's.