Module 1: DATA AND PROCESS MODEL
Module 2: MASTER TABLES AND PAGES
Module 3: DOCUMENTS
Module 4: POSTING
Module 5: FEATURE INTEGRATION
Module 6: REPORTING
Module 7: STATISTICS
Module 8: DIMENSIONS
Module 9: ROLE TAILORING
Module 10: INTERFACES
Module 11: WEB SERVICES
Module 12: TESTING AND DEBUGGING
Module 13: SQL SERVER OPTIMIZATION
- Lesson 1: SQL Server for Microsoft Dynamics NAV
- Lesson 2: Representation of NAV Tables and Indexes in SQL Server
- Lesson 3: Collation Options
- Lesson 4: SQL Server Query Optimizer
- Lesson 5: SQL Server Query Optimizer
- Lesson 6: Data Access Redesign
- Lesson 7: C/AL Database Functions and Performance on SQL Server
- Lesson 8: Bulk Inserts
- Lesson 9: Locking, Blocking, and Deadlocks
- Lesson 10: SIFT Data Storage in SQL Server
- Lesson 11: SQL Server Profiler
Lesson 1: Prerequisite Knowledge in Web Services
Prerequisite Knowledge in Web Services
Prerequisite Knowledge in Web Services : Microsoft Dynamics NAV 2013 supports creating and publishing Microsoft Dynamics NAV functionality as web services. You can expose pages, codeunits, or queries as web services, and even improve a page web service that uses an extension codeunit. When you publish Microsoft Dynamics NAV objects as web services, they are immediately available on the network.
Microsoft Dynamics NAV 2013 web services support the following protocols:
- SOAP (Simple Object Access Protocol) – Publishes pages for create, read, update, and delete access, and codeunits for function call access.
- OData (Open Data Protocol) – Publishes pages and queries for read access.
Web Services Architecture
Web services are a built-in feature of Microsoft Dynamics NAV 2013 Server. They are contained in the same executable file, and run as part of the same service process in Microsoft Windows. By default, when you install Microsoft Dynamics NAV 2013, it is configured to run both SOAP and OData web services. By using the Microsoft Dynamics NAV Server Administration Tool, you may turn either of the web services on or off.
Transactions and State
When you make a web service call, no server state is preserved between the calls. This means that no variables or single-instance codeunits are remembered and no session is maintained. Therefore, each separate web service call is always a single independent transaction.
Security : Every web service consumer must authenticate with Microsoft Dynamics NAV Web services uses all authentication types that are available in Microsoft Dynamics NAV 2013. You can also configure the web services to use Secure Sockets Layer (SSL) encryption. SSL is a cryptographic protocol that provides security and data integrity for data communications over a network. By encrypting the Microsoft Dynamics NAV web services that use SSL, you make your data and the network secure and reliable.
SOAP Web Services
SOAP web services enable full flexibility for building operation-centric services. They provide industry standard interoperability. You can use SOAP to interact with page or codeunit web services in Microsoft Dynamics NAV 2013. SOAP Web services use the Web Service Description Language (WSDL) to describe their data structure and methods.