Jonas Blunck, Senior Test Manager

Esben Nyhuus Kristoffersen,Principal SDE

Developer Guide to Dynamics NAV 2013

Agenda

Dynamics NAV Product Architecture Different Clients Development Environment

Programming Language Object Types

Web Services / OData On-prem vs. Azure Q&A

3

Targeting SMB market

Sold, customized, installed through partners only

Microsoft

Cloud enabled

>80.000 installs>1.000.000 users

Microsoft Dynamics NAV 2013

Available in 40+ countries

Architecture

5

Dynamics NAV 2013 Architecture

SQL Server NAV ServerWeb Client

WindowsClient

DevelopmentEnvironment

Sharepoint Client

6

Platform & Application

Platform Runtime execution environment No source available Developed entirely by Microsoft

Application Built on to run on the platform Tables, Pages, Reports, Codeunits, Queries defining the NAV

ERP application Written in AL using the Dynamics NAV Development

Environment Compiled to .net Source available for customization Customized & Augmented by ISV’s & Partners

Clients in Microsoft Dynamics NAV 2013Clients for your needs – The choice is yours

Users

Benefits

Product

Windows Client

Web Client

SharePoint Client

Full Microsoft Dynamics NAV

application

Full Microsoft Dynamics NAV application in a

web browser

Microsoft Dynamics NAV Portal framework for Microsoft SharePoint

Self Service Applications and Collaboration

Richness, Vividness & User

productivity

Anywhere access through multiple devices with No

client installation

Enhanced Business

Productivity through Microsoft

SharePoint

ERP UserCore ERP UserLight or

Occasional ERP Users or Microsoft

SharePoint Users

Click on icon to change picture

Demo

NAV Clients8

Development

Dynamics NAV Development Environment Integrated specialized Integrated Development

Environment

Definition of Application metadata (e.g. Tables, Reports, ...)

Editing of AL in triggers

In previous versions of NAV also a runtime environment for executing the business logic, but from Dynamics NAV 2013 it’s only a Development Environment

11

7 different object types

Tables - abstraction over SQL tables with additional metadata

Pages - definition of UI Reports - combination of data access and

report layout Queries - SQL queries defined in term of the

table model Codeunits - AL codeunit Xmlports - import/export of xml data Menusuite – definition of navigation tree

12

One definition, Multiple clients

The abstraction level of Pages allows for design once, run on multiple display targets

The Dynamics NAV runtime can render the same Page definition on different targets.

13

Language

AL – Application Language Roots in Pascal Simple Language Powerful through application objects Simple Trigger model

Click on icon to change picture

Demo

Development Environment

14

15

Debugger

All AL code can be debugged All sessions can be debugged

All Clients: Windows, Web or SharePoint Web Services OData requests The “NAS” on NST Background sessions

You can debug a live server Only one user session is affected by debugging Transactions are kept open though

16

Testing

Dynamics NAV 2013 contains a very rich testing framework

Unit testing using TestCodeunits Page Test Transactional Isolation Customizable Reporting using TestRunners

Click on icon to change picture

Demo

Debugging & Testing

17

Reporting and BI

Reporting Ad-hoc Query and Analysis

Charts and Key Performance

Indicators

19

Reporting with Visual Studio and Report Viewer

NAV ServerSQL Server

Visual Studio 2010

Data SetRDLC Layout

Development Environment

Data SetLayout

Windows ClientReport viewer

LayoutData Set

20

Reporting and BI using OData

NAV Server

BrowserPower Pivot & Excel

SQL Server Reporting Services

ODATA

SQL Server

Click on icon to change picture

Demo

Reports & OData

21

On-Premise vs. Azure

23

Dynamics NAV 2013 on-premise

SQL Server NAV ServerWeb Client

WindowsClient

DevelopmentEnvironment

Sharepoint Client

24

Dynamics NAV 2013 on Azure

SQL Azure NAV Azure Instance

Web Client

WindowsClient

DevelopmentEnvironment

25

Deployment is the biggest change, not development Same Platform

On-premise server and Azure instance shared 99% of codebase.

Same Application Some integration scenarios will not work on Azure (the

Azure host environment is different from on premise)

Same SQL tables although some constraints on SQL Azure

Same clients Sharepoint can’t be deployed to Azure

NAV on Azure topology

SQL Azure Worker Role

Web Client(Browser)

WindowsClient

DevelopmentEnvironment

Web Role

Web ServiceoData

27

Azure Deployment

What do you need? Azure account 3 files (.cspkg, .bacpac, .cer) 2 steps (initial upload, creating new instances)

Result 1 Url

Client Windows Client Web Client (Browser)

28

Authentication

Dynamics NAV 2013 supports multiple authentication schemes

Active Directory This is used for on-premise installation where users are

mapped to local domain accounts.

Username/Password Simple authentication model. Easy to configure

ACS – Access Control Service Supports OAuth 2.0, WS-Trust, and WS-Federation protocols and

the SAML 1.1, SAML 2.0, and Simple Web Token (SWT) token formats

Integrated and customizable Home Realm Discovery so users can choose their identity provider with support for Windows Live ID, OpenID 2.0, Google, Yahoo, Facebook, and enterprise providers such as Windows Active Directory.

Click on icon to change picture

Demo

Azure

29

Q&A