Dynamics™ NAV Architecture |
| Microsoft Dynamics NAV 2009 offers you the choice to stay with the Dynamics NAV Classic client or move to the RoleTailored client: | |
One Solution: |
|
|
Same application Same development Same Office integration Same Outlook integration |
![]() |
Dynamics NAV Three Tier Architecture: |
|
|
Presentation Layer |
|
![]() |
|
Architecture Comparison |
Forms and Pages |
|
| Classic Client | RoleTailored Client | Classic Client uses Forms |
|
C/SIDE Client Authorisation/ Authentication Application Objects Presentation Layer Code, Triggers, Validation |
RoleTailored
Client Metadata New Presentation Layer Simple type validation |
- Forms are objects with statically defined
UI elements – WYSIWYG - Forms state (memory) is held entirely on the client - Non validation code not encouraged but allowed |
|
NAV Service Tier |
Role Tilored Client uses Pages |
|
|
Authorization/ Authentication Application Objects Code, Triggers, Validation Web Services |
- Structural xml-like definition - Pages can be interpreted by different client types
allowing them to be reused by NAV Portal and for Web Services - Page state (memory) held on both client and NST - Fewer triggers than Forms but code is allowed |
|
| Database Server | Database Server | |
|
C/SIDE Server or SQL 2005/8 |
SQL Server 2005/8 |
|
Platform Features |
Microsoft Dynamics NAV Server Goals |
|
| Web Services: | NAV 2009 Technology Goals: | |
| Industry Standard (Basic Profile) - Office, Sharepoint, Infopath - 3rd Party vendors - Easy to publish - Focus point for integrations - Eventual replacement for NAS Business Oriented - Complex Data types - Header Lines relationships - Validation & Triggers Reports - Based on SQL Report Control - Colourful Charts and Graphs - Interactive - Show and hide by expanding/collapsing line information - Dynamic Sorting Re-use the code environment from C/SIDE Development Environment Re-use much of existing report definitions Use Visual Studio to define the layout |
- Support new Role Tailored User Experience (UX)Provide Web
Services - Minimize changes in C/AL code from C/SIDE architecture to run on Dynamics NAV Server - Provide development tools (object designers) for new platform features - Leverage .NET Framework for application runtime |
|





