Microsoft Dynamics NAV Versions List
Microsoft Dynamics NAV is Enterprise Resource Planning ( ERP ) software for Mid Size Companies provided by Microsoft Cooperation. Dynamics NAV started journey from 1985.
This page gives a brief history of the versions of Navision. Which has had a very colorful history of changing its name further down is a list of all the versions of “Navision” that have been released over the years.
|Dynamics NAV 2016|
Dynamics NAV Versions List
PC Plus (1985)
Navigator (ver 1 and 2 1987) This name used in Denmark
IBM Navigator (ver 3.00 thru 3.04 1990) This name used in Denmark
Navigator (ver 3.50 thru 3.56 1994) This name used in Denmark
Fjödiner (1990) This name used in Iceland
Avista (1992) This name used in The USA
Navision for Windows (3.1 1993) Product prototype never released
Navigator Financials (0.9 thru 2.6 1994) This name used in Denmark
Navision Financials (1.0 thru 2.60 1995)
Avista Financials (1.1 thru 1.2 1995) This name used in The USA, but
Fjödiner Financials (help me here) This name used in Iceland
Navision Solutions (ver 3.00 2000)
Navision Attain (ver 3.01 thru 3.10 2001)
Navision (ver 3.60 thru 3.70 2003)
MBS Navision (marketing name only)
Dynamics NAV (4.00 2005)
Dynamics NAV 5.00 (2007)
Dynamics NAV 5.1 (Dynamics NAV 2008) (canceled)
Dynamics NAV 6.0 (canceled)
- Dynamics NAV 2009: (“6.00”) 2009, 2009 SP1, 2009 R2
- Dynamics NAV 2013: (“7.00”) 2013, (“7.1”) 2013 R2
- Dynamics NAV 2015: (“8.00”) 2015
- Dynamics NAV 2016: (“9.00”) 2016
- Dynamics NAV 2017 (Upcoming Version not yet released)
DOS and the predecessors to Navision as a true ERP package.
Navigator 1 when introduced in 1987 was very much ahead of its time, with features such as:
Client/Server (possibly the first every client server based accounting package)
The 2.xx version again was a Danish product, sold under the name of IBM Navigator. It came with he ability to write your own reports, and make some changes to the database it self. The biggest thing is that it was a full Client/Server multi user package. It introduced the basis of the version principle. It also had a form of Flow Field technology that allowed some analytical reporting.
This could be considered as the first True product that is Navision as we know it today. it introduced a full IDE (Integrated Development Environment). This allowed partners to modify the system and make very deep customizations for their clients. This was all handled in the AL Programming Language, meaning Application Language. AL was never designed as a development language, but as a tool to make it simple and easy to make changes to the Navigator business logic.
General release version. This version included many minor fixes and functionality tweaks. This was the product first named “Navision”, and really is the product that put PC&C and Navision on the map.
AL Programming Language
Design Tools – Screens, Tables, Reports, Imports, Batches and Functions.
Structured exception handling
This version was designed as a cross platform system, introducing (beyond OS/2 and DOS), support for Unix and integration with other products.
Unix version AIX
Navision ODBC interface
Support for Oracle and Informix as the backend server.
Windows NT client server support.
Native support for Windows NT is released. Running the old DOS extended version under NT, or the OS/2 version in compatibility mode is no longer required.
Prototype only, never released.
After further work, and looking at other Screen scraper products int he market, Navision decide that they should continue to sell the existing Text based product, and develop a full 16 bit Windows 95 product.
In 1995, Navision released its first true windows version.
A key target for Navision is to gain the “Made for Windows 95” logo. Navision is the first Accounting package to receive this logo. The product has a very “MS Office” look and feel, and is used by Microsoft Partners to demonstrate Windows 95.
The new version of AL is very well executed, though has a couple of major bugs. And there is no report designer.
1996. Very buggy product (0.9 the beta version was actually more stable). users on this version have a lot of problems to move, and often clients had to start their implementation from scratch to move to 1.1
No upgrade path from DOS to 1.0
Generally looked up as “The Upgrade version” this product became the starting point if you moved from DOS to windows.
Limited release version. This product introduced Human Resources, which in reality was a stripped down component of the US payroll system. Added to the W1 version to make management of Payroll implementations easier.
Significant changes include a whole new method of generating document numbers. Whilst functionally powerful, it introduced a lot of serious locking issues that remain with Navision even today.
Primarily released for the US market because of delays in getting 1.30 ready to release, and the long gap since the release of 1.10
In the Financials world (except The USA), Version 1.3 was the base on which Navision moved forward. This version was very fast and simple, the code was easy to follow, and very reliable. Possibly the most stable of all Navision products.
Substantial changes made to posting group setups. International version not released in the US.
Not officially released.
EUR conversion and Y2K. 2.00 was virtually the version previously known as 1.40; the renumbering was done to indicate the importance of the Euro. Unofficially, it was pushed by some partners as the Year 2000 (Y2k) version even though ALL products from PC C had always been Year 2000 compatible.
For most people 2.01 is thought of as the version where the Print Button finally works. Although not a major issue, it was very frustrating to have a print button that does nothing. Also OnTimer on forms. Interestingly the developement team were told that they were allowed to fix 80 bugs or issues in Navision 2.00, so they traveled and asked many partners for advise as to which 80 bugs should go on the list. A working Print button was by far the number on request.
Customers on 2.50 SQL had serious consistency issues, and were advised to move to 2.60 ASAP
Following the SQL issues, and numerous other bugs in 2.50, Navision release 2.60 very soon after 2.50. It is apparent very quickly that for the Native Database, 2.60 is an extremely stable product. The reputation of Navision continues to grow. Very little new functionality is added, but just about everything is fixed (so long as you don’t like Average costing).
This is traditionally one o the most reliable Navision products.
Navision generally has a reputation of delivering simple reliable fast software. 2.60 AD broke all these traditions. The design was poor, and even if you did not activate the AD functionality, the system was extremely slow and very buggy. The AD modifications did not follow Navision Guidelines, and data corruptions became very common. Core to most of the problems, was extensive modification of Tables 36 and 37 to do things they were never designed for, like transfers.
General consensus would put this as the most buggy and by far worst version of Navision ever released.
A core issue of 2.60AD is that the Advanced Distribution enhancements very rarely fit to a companies needs, but making even the slightest code change generally had an on going domino effect such that the NSC would be continually fixing bugs.
2.60M was 2.60 with the Manufacturing Add-On integrated. It basically worked, but was generally too slow to work for the companies it was designed for, so was not too successful. It did though give a good test base for the future version to come.
The first Commerce Gateway release. (Courtesy of bbrown)
Navision Solutions. Actually this limited release version, I have never seen installed at a client site. I am not sure if this was ever even supposed to be sold.
The version appeared more to be a NSC Preview version to prepare staff for what was to come. In that regard it sort of did the job, but was not complete enough to train on, so not of great benefit.
Introduces Navision Application Server
The move to having Ledgers broken into two separate tables (one for the transaction it self, and one for the Accounting value) is finally solved and working. 3.10 is missing a few things, bins being the most significant, but other wise this is a great product. I know clients that installed it when it was first released, and are still very happy on it today. Sales Tax rounding is an issue in the US.
Manufacturing now works, and is a serious product for real manufacturing companies.
3.70 was a significant version release for Navision. with 3.70 and the service packs A and B, many of the bugs introduced since 3.00 were now resolved, and this product put Navision back on the path of delivering solid, reliable software.
Mainly bugfix release. Many changes to Warehouse Management to improve integration & performance on SQL.
Introduces Industry Template Solutions. Commerce Gateway supports Microsoft Biztalk Server 2004. Numerous bugfixes.
Introduced the Menu Suite, which completely changed the menu structure of the product. This was the first step in making the menu role-oriented instead of functionality oriented. This was very hard for both existing users and consultants to accept. A lot of companies postponed or canceled upgrades from previous versions because of a fear of extended training needed – “just” because of the new menu structure.
Although not actually a new version of Navision, this service pack was more than many new versions in Navision. Thus it is being included as a version rather than just a service pack.
Fix to the SQL security model.
The most significant feature of this version, is that for the first time in the History of NAV, Sift Technology is no longer available. Instead Indexed views are used. For more information see the Dynamics NAV 5.00 sp1 article.
Canceled. (renamed to NAV 6.00)
Canceled. (renamed to NAV 2009)
The first release of the Three Tier Client has been officially renamed to Microsoft Dynamics NAV 2009 the release was announced in October 2008 at Convergence in Denmark.
This version is the first major rewrite of the Navision product since Navision Financials.