Some basic things to know before working on MS Dynamics NAV

To know which version of MS Dynamics you are using-

Click on Help and select ‘about Microsoft dynamics NAV development environment’

A window appears which shows the latest version you have been upgraded and the product is licensed to Microsoft and some more information.

Difference b/w version and version list in MS Dynamics NAV

Version	Version List
It displays the latest version i.e. being used in MS Dynamics NAV (upgraded version)	It displays the version of various objects which were added some extra features. It differs from 1 object to another or from 1 field to another.
It shows licensed information	It doesn’t show any such things
We can’t edit in version window	We can edit in version list column
It is used to know the details of which version we’re using	It used mainly to update the changed information. Ex. Suppose developer ‘A’ will change a customer table and move to some other project after few months. To know which table the developer modified we edit version list column. (if the version list of column is 12345.34, we edit it has name,12345.34. So that we will come to know who actually modified which column)

Some rules to be followed while changing field id or table id

Suppose we are modifying any existing table i.e. created by Microsoft then the field no. of that existing table should be between 50,000 to 99,999 disagreeing this will lead to compile time error.

Suppose we are creating any new table then the table id should be assigned the no. b/w 50,000 to 99,999 disagreeing leads to CTE.  If we’ve created a new table then that field no. can take any no > 0. To know more about this id go through architecture of NAV.

Do’s and Don’ts while working on NAV IDE

·         Don’t compile and save if you have not did any changes on objects.

·         If you save and compile without any changes then there will be a check mark on the modified screen. Other developers will get confused and waste their time by also reviewing this unchanged saved object. (instead just escape if you are not changing any fields)

·         All the table name, field name and word after space should begin with capital letter.

Locked and Unlocked

When several developers use the same database then it’s better to lock and work by particular developer so that no one except him can edit or modify or save. Others can only view the locked content but cannot modify.

Only the locked developer can unlock. If there’s any case to unlock when the locked developer is not available then you can choose forced unlock option.

Import and export to and from the file.

Import means uploading any file from drive to nav software.

Export means saving a file from nav software to drive.

Extensions used in dynamics NAV

License file is stored as .flf

In 2009 native db was saved as (.fdb) now in 2015 its no more used.

Objects are saved as .fob

Note: Its better to save any object you are using both in .fob and .txt format.

Toggle mark

Sometime there arises a case to save 3 or more object elements to a single file we do this by using toggle mark (to select object elements we need to save), go to view click marked only and click all button below objects window then select all and save to your desired location.

Difference b/w upload and change in license information

Change will only affect table or any other objects but changes are not made at role tailored client.

Upload will do changes both on objects elements and also on role tailored client.

Know More-

Option - It will show some information, path where we’re saving etc.

Autolock - will automatically lock your data’s so that it cannot be modified by anyone.

Prevent data loss from table - you cannot delete any fields which you created.