• Presentation level (RoleTailored client)


• Business logic and communication level (Microsoft Dynamics NAV Server)


• Data level (SQL Server database)

The different tiers can be installed on different computers. You can have multiple instances of any of the components (though usually not on the same computer): multiple clients, multiple servers, and multiple database servers.
Here's a simple installation with two SQL Server database computers, each associated with a single Microsoft Dynamics NAV Server computer, each of which in turn supports two Microsoft Dynamics NAV RoleTailored clients:

RoleTailored Architecture Components
The components that make up the RoleTailored architecture in Microsoft Dynamics NAV 2009 are:

• RoleTailored Client


• Microsoft Dynamics NAV Server


• Database Components and SQL Server

RoleTailored Client

Let us take a simple report with customer and Cust. Ledger Entry as dataitems. Cust. Ledger Entry is linked to Customer using Customer No. Suppose there are only two records in the Ledger Entry table.

• OnInitReport


• OnPreReport


• Dataitem--> Customer--> OnPreDataitem


• Dataitem--> Customer--> onAfterGetRecord


• Section--> Customer Header --> OnPreSection


• Section-->Customer Header --> OnPostSection


• Section-->Customer Body --> OnPreSection


• Section-->Customer Body --> OnPostSection


• Dataitem--> Cust.Ledger Entry --> OnPreDataitem


• Dataitem-->Cust.Ledger Entry --> onAfterGetRecord


• Section--> Cust.Ledger Entry header--> OnPreSection


• Section--> Cust.Ledger Entry header--> OnPostSection


• Section--> Cust.Ledger Entry body --> OnPreSection


• Section--> Cust.Ledger Entry body --> OnPostSection


• Dataitem --> Cust.Ledger Entry --> onAfterGetRecord


• Section --> Cust.Ledger Entry body --> OnPreSection


• Section --> Cust.Ledger Entry body --> OnPostSection


• Dataitem--> Cust.Ledger Entry --> OnPostDataitem


• Dataitem--> Customer --> OnPostDataitem


• OnPostReport

• You can select the FILE→IMPORT/EXPORT and TOOLS→TRANSLATE→ IMPORT/EXPORT OPTIONS.
• You can compile MenuSuite objects (F11 or TOOLS→COMPILE). It is the object references that are compiled. If the MenuSuite object contains a reference to a nonexistent form, report, batch job, dataport or codeunit, a compilation error occurs.

The रन button in the Object Designer is disabled when you click the MenuSuite button because a MenuSuite object cannot be run.

VARIABLEACTIVE (Automation)

Use this function to determine if a variable, such as field or a control, is active or inactive.
IsActive := VARIABLEACTIVE(Variable)
IsActive
Data type: boolean
The result.

Creates Line No. automatically for new new record

Navision can automatically assign Line No. to a new record if the Line No. is part of the primary key fields. This can be done by setting the AutoSplitKey property in the Form to Yes. By default the AutoSplitKey property is set to No.

Let's consider the following example. When I enter a new sales line record in Sales Order form, Navision will automatically assign Line No. = 10000 to the first Sales Line record. Now, if I enter the 2nd Sales Line record, Navision will automatically assign Line No. = 20000 to the new record. If I insert a new record between the 1st and 2nd record, Navision will automatically assign Line No. = 15000 to the new record.

All this can happen because Autosplitkey property in Form 46 - Sales Line is set to Yes. In order for AutoSplitKey feature to work, the last field in the primary key must be an integer, BigInteger, GUID or decimal field. If you look at the Sale Line table, the Primary key is 'Document Type,Document No.,Line No.', where Line No. is an integer field.

Diffrence Between Two Tier And Three Tier Architecture in Microsoft Dynamics NAV(Navision)

• Prepare to install the SSIS Package.
• Install the SSIS Package.
• Configure the SSIS Package.

To prepare to install the Microsoft SQL Server Integration Services Package

• If the Microsoft Dynamics NAV database contains pictures that will be stored on the mobile staging database and replicated on mobile devices, you need to verify that picture files are not compressed in Microsoft Dynamics NAV. To verify or modify the compressed setting, complete the following steps:

1. In Microsoft Dynamics NAV client, click Tools, and then click Object Designer.
2. Click Tables, select the Item table, and then click Design.
3. Select Picture and then click Properties from the toolbar (SHIFT+F4).
4. Set the Compressed property to No.

• Verify the following:

1. The mobile staging database requirements are met. For more information, see Mobile Staging Database and SQL Server Integration Services Prerequisites.
2. The mobile staging database is created. For more information, see How to: Create the Mobile Staging Database, Database Objects, and the Mobile Staging Publication for Mobile Sales and Configuring the Mobile Staging Database and SQL Server Replication.
3. Microsoft Dynamics NAV database has been updated with the necessary tables. For more information, see Installing Microsoft Dynamics NAV Integration

For More Information visit:http://msdn.microsoft.com/en-us/library/cc563940.aspx

INCONSISTENCY Error in Navision Occur because of the following reason.

Posting invoices writes to the G/L entries and the total must ALWAYS be 0.
Somewhere an amount is written but it has no opposite to make the total 0.
This means that there is a problem with some customization of the code.

This is a trick I use whenever I do try to solve and see why you the db is getting CONSISTENT Error.
I create the following CU.

OBJECT Codeunit 50000 Single Instance CU
{
OBJECT-PROPERTIES
{
Date=10/11/07;
Time=[ 2:50:02 PM];
Modified=Yes;
Version List=MOD01;
}
PROPERTIES
{
SingleInstance=Yes;
OnRun=BEGIN
IF NOT StoreToTemp THEN BEGIN
StoreToTemp := TRUE;
END ELSE
FORM.RUNMODAL(0,TempGLEntry);
END;

}
CODE
{
VAR
TempGLEntry@1000000000 : TEMPORARY Record 17;
StoreToTemp@1000000001 : Boolean;

PROCEDURE InsertGL@1000000000(GLEntry@1000000000 : Record 17);
BEGIN
IF StoreToTemp THEN BEGIN
TempGLEntry := GLEntry;
IF NOT TempGLEntry.INSERT THEN BEGIN
TempGLEntry.DELETEALL;
TempGLEntry.INSERT;
END;
END;
END;

BEGIN
END.
}
}



And in CU 12 I add the following Code in function FinishCodeunit

FinishCodeunit()
WITH GenJnlLine DO BEGIN
IF GLEntryTmp.FIND('-') THEN BEGIN
REPEAT
GLEntry := GLEntryTmp;
IF GLSetup."Additional Reporting Currency" = '' THEN BEGIN
GLEntry."Additional-Currency Amount" := 0;
GLEntry."Add.-Currency Debit Amount" := 0;
GLEntry."Add.-Currency Credit Amount" := 0;
END;
GLEntry.INSERT;
//MOD01 Start
SingleCU.InsertGL(GLEntry);
//MOD01 End
IF NOT InsertFAAllocDim(GLEntry."Entry No.") THEN


Once you've made the changes. You run the SinleInstanceCU Once.
Then do what ever you do to get the consistency error.
Then Run the SingleInstanceCU again.
You'll see a list of GL lines. You will see why the transaction is not balanced.