Jonas Blunck, Senior Test Manager Esben Nyhuus Kristoffersen, Principal SDE

1. Jonas Blunck, Senior Test Manager Esben Nyhuus Kristoffersen, Principal SDE Developer Guide to Dynamics NAV 2013

2. Agenda • Dynamics NAV Product • Architecture • Different Clients • Development Environment • Programming Language • Object Types • Web Services / OData • On-prem vs. Azure • Q&A

3. Microsoft Dynamics NAV 2013 Targeting SMB market >80.000 installs >1.000.000 users Microsoft Available in 40+ countries Sold, customized, installed through partners only Cloud enabled

4. Architecture

5. Dynamics NAV 2013 Architecture Windows Client Development Environment Web Client Sharepoint Client SQL Server NAV Server

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

7. Clients in Microsoft Dynamics NAV 2013Clients for your needs – The choice is yours Windows Client Web Client SharePoint Client • Light or Occasional ERP Users or Microsoft SharePoint Users • Core ERP User • ERP User Users • Full Microsoft Dynamics NAV application in a web browser • Microsoft Dynamics NAV Portal framework for Microsoft SharePoint • Self Service Applications and Collaboration • Full Microsoft Dynamics NAV application Product • Anywhere access through multiple devices with No client installation • Enhanced Business Productivity through Microsoft SharePoint • Richness, Vividness & User productivity Benefits

8. NAV Clients Demo

9. Development

10. 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

14. Development Environment Demo

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

17. Debugging & Testing Demo

18. Reporting and BI Reporting Charts and Key Performance Indicators Ad-hoc Query and Analysis

19. Reporting with Visual Studio and Report Viewer Development Environment Visual Studio 2010 Windows Client Layout Data Set RDLC Layout Layout Report viewer Data Set Data Set SQL Server NAV Server

20. Reporting and BI using OData Power Pivot & Excel SQL Server Reporting Services SQL Server ODATA Browser NAV Server

21. Reports & OData Demo

22. On-Premise vs. Azure

23. Dynamics NAV 2013 on-premise Windows Client Development Environment Web Client Sharepoint Client SQL Server NAV Server

24. Dynamics NAV 2013 on Azure Windows Client Development Environment Web Client SQL Azure NAV Azure Instance

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

26. NAV on Azure topology SQL Azure Worker Role Web Role Web Service oData Windows Client Web Client (Browser) Development Environment

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.

29. Azure Demo

30. Q&A