Dynamics NAV 3 tier architecture

At the Data Layer: Various information and records are stored in a database called SQL Server.

At Business Logic Layer: Execution of database logic at Business Logic Layer will happen by accessing SQL Server from Data Layer.

At Presentation Layer: after the execution of database in Business logic finally logic is displayed on the output screen which is visible to the user in user friendly mode.

As we see in the figure, the objects are differentiated into 4 categories,

In an Client Server IDE we have,

World wide generic objects:

Assume, Microsoft Dynamics developers team will start developing a product at their HQ in U.S.A, they will have some generic objects such as tables, pages, xml ports, data ports and so on..

These objects are marked in diagram with dark boxes.

Each object will have its own ID with some range.

Country-Specific Objects:

The product which has objects that were developed by Microsoft developers team will be transferred to various countries. (Say India) so, if the tax at U.S is 8% in India the tax for product will be say 14%.

So, Indian developers need to write a tax code for that existing object(means they’re modifying the object details here).

These objects are with light dark boxes in diagram.

Customer Specific Objects:

Suppose the product which is modified by Indians are now to be adopted for particular company of India. Customer need that product a/c to their requirement like trademark on the product or a company logo.

These objects are with bit light boxes in diagram.

The range of Customer Specific object is: 50,000 to 99,999( within this ID we can create any object) out of this range you cannot create an object but u can modify the object i.e out of range.(ex. Object ID of 14 can be modified in C.S.O but cannot be created)

The range of Country Specific object is: 10,000 to 49,999

The range of World wide generic object is: everything else.

Let me not discuss about vertical solutions object now.