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 2: Debugging
Debugging : The process of finding and correcting errors is called debugging. Microsoft Dynamics NAV 2013 provides an integrated debugger to help you inspect your code to verify that your application runs as expected. The debugger user interface (UI) runs in the Microsoft Dynamics NAV 2013 client for Windows. The debugger services run in the Microsoft Dynamics NAV Server.
Activating the Debugger
When you activate the debugger, you start it. When you start the debugger, it can be in one of the following states:
- Attached to a session.
- Waiting to attach to a session.
To start the debugger in the Microsoft Dynamics NAV 2013 Development Environment, in the Tools menu, click Debugger > Debug Session. This opens the Session List window that shows all debuggable sessions that currently run on the same Microsoft Dynamics NAV 2013 server instances on the local machine instance as the debugger . This is the same instance that is targeted when you use the Run action on Application objects in the Object Designer window.
In the Session List page, you attach the debugger to a session by doing one of the following:
- Select a specific session, andthen click Debug.
- Click Debug Next, and then start a new session.
After you start a debugger, the Debugger page opens. You use the Debugger page to manage the debug process as follows:
- Step through the code.
- Manage the code execution.
- Manage the breakpoints.
- View the variables in scope of the current line.
- View the last error message.
- Manage watches.
- View the call stack.
You can break code execution of the session that you are debugging by doing the following:
- Setting a breakpoint on a line of code.
- Specifying a break on the next statement.
- Specifying a break on errors.
- Specifying a break on record changes.
You can set breakpoints before you start a debugging session or when you are debugging. Breakpoints and break rules are applied immediately in the session to which the debugger is attached.
The debugger usually stops on breakpoints. However, you can enable other break rules that enable the debugger to do the following:
- Stop on error.
- Break on record changes.
- Skip any breaks in Codeunit 1.
To define these additional rules in the Debugger page, click Break Rules. It opens the Debugger Break Rules dialog box.