Force.com IDE Developer Guide
jWinter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
Spring '16 (API version 36.0)
Winter '16 (API version 35.0)
Summary of Getting Started with the Apex Debugger
Contact Salesforce to Enable the Apex Debugger
Install or Update the Force.com IDE Plug-In for Eclipse
Set Up a Permission Set
Create a Project
Test Your Debugger Setup
Whitelist Users and Request Types
Manage Debugging Sessions
Set Up the Apex Debugger
Complete these tasks to get the Apex Debugger ready for use in
your Salesforce org and on your
workstation.
-
Contact Salesforce to Enable the Apex Debugger
Some services and subscriptions include this feature for an extra cost. For pricing details, contact your Salesforce account executive. -
Install or Update the Force.com IDE Plug-In for Eclipse
The Apex Debugger is part of the Force.com IDE plug-in for Eclipse. Before you set up the Debugger, install or update the Force.com IDE. -
Set Up a Permission Set
Create a permission set for Apex Debugger users, and assign it to any users in your org who plan to use the Debugger. -
Create a Project
If you’re new to using the Force.com IDE, set up a project. If you plan to debug an existing Force.com IDE project, skip these steps. -
Test Your Debugger Setup
To make sure that everything is functioning properly, create a simple Apex class, set a breakpoint in your code, and then hit the breakpoint using Execute Anonymous. -
Whitelist Users and Request Types
Filter which requests are debugged by setting up whitelisting. If you don’t use whitelisting, all events in your org trigger debugging during a debugging session. Whitelist users or request types to focus only on the events that are relevant to the problem you’re debugging.