Version: Available or changed with runtime version 1.0.
Enables communication with a debugger.
Note
This data type is supported only in Business Central on-premises.
Static methods
The following methods are available on the Debugger data type.
| Method name | Description |
|---|---|
| Activate() | Activates the debugger and attaches the debugger to the next session that is started. |
| Attach(Integer) | Activates the debugger and attaches it to the specified session. |
| Break() | Breaks code execution of a debugging session. |
| BreakOnError(Boolean) | Sets whether the debugger breaks on errors. |
| BreakOnRecordChanges(Boolean) | Breaks execution before a change to a record occurs. |
| Continue() | Executes code until the next breakpoint or until execution ends. |
| Deactivate() | Deactivates the debugger. |
| DebuggedSessionID() | Gets the ID of the previous session that the debugger was attached to. |
| DebuggingSessionID() | Gets the ID of the session that the debugger is currently attached to. |
| EnableSqlTrace(Integer [, Boolean]) | Enables or verifies SQL tracing. If you enable SQL tracing, then SQL Server events for selected sessions on the server instance are collected. |
| GetLastErrorText() | Gets the last error that occurred in the debugger. |
| IsActive() | Indicates whether the debugger is active. |
| IsAttached() | Specifies if the debugger is attached to a session. |
| IsBreakpointHit() | Specifies if a breakpoint is hit in a debugging session. |
| SkipSystemTriggers(Boolean) | Enables the debugger to skip code that is inside system triggers. |
| StepInto() | Executes a method call and then stops at the first line of code inside the method. |
| StepOut() | Enables debugging to return to the calling method after it steps into a method call. |
| StepOver() | Executes a method call and then stops at the first line outside the method call. |
| Stop() | Stops execution as if the code hits an error. |
Note
The Dynamics 365 Business Central Debugger is an example of a debugger application that is built using tables, pages, codeunits, and the AL debugger methods.