1. Instructions You must bring your own laptop, your presentation and a power supply Technical staff is present in all to assist with network, audio and video setup Speakers are responsible for presentation computer and demo equipment Please make sure your PC have correct video drivers installed. Be at your session no later than 30 min. Prior to your timeslot to setup your equipment Evaluation-slide will be send to you prior to Campus Days, which should replace the current Evaluation-slide Technical details All presentations should be 16:9 widescreen format Output connectors provided in all session rooms are: DVI, HDM, Micro HDMI, VGA For NON-Microsoft speakers: Own company logo is allowed on the Session Title slide only Sessions are non commercial – Please do NOT sell own products or services

4. Working with Odata og Web Services i NAV 2013 R2 Introduction to Introduction to SOAP and OData Web Services What is possible with capabilities in NAV 2013 Integration with to multi-tenant NAV 2013 R2 on on Azure Writable OData in Writable NAV 2013 R2

5. Introduction to OData and SOAP

6. SOAP services Operation oriented High flexibility Custom code needed NAV support Pages and Codeunits OData services Resource oriented HTTP transport Standard tools exist NAV support Pages and Queries

7. Demo Simple BI in Excel and building a simple LightSwitch application

8. After a successful deployment remember to… Check the endpoint settings for virtual machine Map the internal endpoints to the public facing endpoints Ensure that communication is secured with a certificate. and that certificate is trusted by the clients. Update the public SOAP and OData URLs

9. One consolidated way of generating URLs New method in AL May require changes to configuration files to get to correct external address Visible in ‘About this Page’ and the ‘Web Services’ page : / /OData/ For example https://Cronus.Nav.net:7048/dynamicsnav/OData/ --> : / /WS/ For example https://Cronus.Nav.net:7047/dynamicsnav/WS/ -->

10. Demo Seeing the URLs in the product

11. Certificates are used in these scenarios Windows and Web clients: Non Windows authentication, in order to protect the users credential. SOAP and OData clients: For all authentication types, in order to protect all communication. Exception would be in a domain where IPSec has been enabled. Walkthrough: Configuring Web Services to Use SSL (SOAP and OData)... Walkthrough: Configuring Web Services to Use SSL (SOAP and OData) or use Microsoft Dynamics NAV 2013 R2 Administration tools

12. Demo Secure the communication with certificates

13. Tenant id is used in two places… The query string of the URL has a Tenant parameter = http://...?tenant=defaulthttp://...?tenant=default Users are created pr. tenant. Credentials dialog is needing the tenant id, in order to authenticate the user against the correct tenant. Format: Username = Tenant\[Domain]\Username + Password = ********

14. Tenant id with different Authentication schemes… Windows or UserName Use URL with a Tenant parameter = http://...?tenant=defaulthttp://...?tenant=default NavUserPassword or AccessControlService Credentials dialog with tenant id : Username = Tenant\[Domain]\Username + Password

15. Demo Connecting to a specific tenant from Excel

16. Licenses has a scope of Server, Database or Tenant. License Type: External (customers) grants access to SOAP and OData clients only. License Type: Full User and Limited User login information is cached for all SOAP and OData users, and is removed again after 2 hours of inactivity.

17. Demo License rules for SOAP and OData

18. NAV 2013 R2 allows you to modify data in pages through PUT, POST requests All validation logic in the pages are run NAV Permissions are applied Concurrency is controlled by an ETag property Update and Delete will cause an error if ETag does not match

19. OData callData impactTriggers run POSTCreates a new entityOnNewRecord and OnInsert PUT and MERGEModifies the specified existing entityOnModify DELETEDeletes the specified entityOnDelete

20. Demo Writing data to NAV through a LightSwitch application

21. Language-Integrated Query Standard, easily-learned pattern for querying and updating data Extensible to support almost any kind of data store Works very well with OData sources

22. Demo Using LINQ queries from C#

24. Office Apps – e.g. display customer information in emails Mobile apps – simple lookup and editing scenarios Data synchronization – e.g. using the NAS Embed NAV data in Sharepoint using BCS Integrate into anything that takes an Odata source Distribute BI views of your data in Excel sheets

25. Evaluation Create a Text message on your phone and send it to 1919 with the content: CN307 5 5 5 5 I liked it a lot Session Code Jens Performanc e (1 to 5) Match of technical Level (1 to 5) Relevance (1 to 5) Comments (optional) Evaluation Scale: 1 = Very bad 2 = Bad 3 = Relevant 4 = Good 5 = Very Good! Questions: Speaker Performance Relevance according to your work Match of technical level according to published level Comments Stefan Performanc e (1 to 5)

26. © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.