Premanath Kumarage

MS Dynamics NAV – Setting up an Application Server (NAS) In MS dynamics NAV, there are lots of discussions about NAS and its behavior & functionality and also about installing NAV correctly. Lets’ first see what is meant by NAS? What is NAS? Navision Application Server is a middle-tier server that runs as a service. It is designed to provide access from external clients to the MS Dynamics NAV Navision database. The database could be either MS SQL Server or Native Navision Database Server. Whatever database platform it runs, NAS acts as a bridge to the NAV database when it is integrated other external applications. In this case, external applications mean any other applications apart from the typical Navision client. The key role of the application server is in the e-business solutions. For example, Navision Application Server provides connectivity between a Web client (such as Navision Employee Portal) and Navision Database Server; between an external application (such as Microsoft...

MS Dynamics NAV – Setting up an Application Server (NAS) In MS dynamics NAV, there are lots of discussions about NAS and its behavior & functionality and also about installing NAV correctly. Lets’ first see what is meant by NAS? What is NAS? Navision Application Server is a middle-tier server that runs as a service. It is designed to provide access from external clients to the MS Dynamics NAV Navision database. The database could be either MS SQL Server or Native Navision Database Server. Whatever database platform it runs, NAS acts as a bridge to the NAV database when it is integrated other external applications. In this case, external applications mean any other applications apart from the typical Navision client. The key role of the application server is in the e-business solutions. For example, Navision Application Server provides connectivity between a Web client (such as Navision Employee Portal) and Navision Database Server; between an external application (such as Microsoft...

Let’s see the main steps involved during a version upgrade. In this case, it is assumed that the customer is running a version of Microsoft Business Solutions Navision 3.7 or more. 1. Get a backup of the current customer database and restore it in a 2009 client. 2. Identify all the objects modified in the customer database. For this process, Developer Toolkit for MS Dynamics NAV is recommended and all modifications that are done in the current client installations will be highlighted by the Developer Toolkit. Text form all objects files of both current customer database and cronus database should be provided to the Developer Toolkit as the inputs. 3. Analyze the modifications in the customer db and decide whether they are really required in the new version. For example, similar functionality may have been introduced by the new version. In such cases the modifications done in the old version may become obsolete. For example, from ver. 3.6 to NAV 2009 several areas have been redesigned a...

Let’s see the main steps involved during a version upgrade. In this case, it is assumed that the customer is running a version of Microsoft Business Solutions Navision 3.7 or more. 1. Get a backup of the current customer database and restore it in a 2009 client. 2. Identify all the objects modified in the customer database. For this process, Developer Toolkit for MS Dynamics NAV is recommended and all modifications that are done in the current client installations will be highlighted by the Developer Toolkit. Text form all objects files of both current customer database and cronus database should be provided to the Developer Toolkit as the inputs. 3. Analyze the modifications in the customer db and decide whether they are really required in the new version. For example, similar functionality may have been introduced by the new version. In such cases the modifications done in the old version may become obsolete. For example, from ver. 3.6 to NAV 2009 several areas have been redesigned a...