Salesforce Web Console (Beta) is a browser-based development environment that allows developers to write Apex code, run queries, debug applications, and manage metadata directly within their org. It is designed as a modern alternative to older tools such as Developer Console and Workbench.
The Salesforce Web Console is available directly inside Salesforce and does not require additional installations. Developers can execute Salesforce SOQL queries, edit Apex classes, retrieve metadata, and perform other development tasks from a single interface.
In this guide, we’ll go through the setup process and explore how to use the Salesforce Web Console for coding, debugging, query execution, and metadata management.
How to Set Up and Use Salesforce Web Console (Beta)
Getting started with the Web Console takes only a few minutes. Follow the steps below to enable the feature in your Salesforce org and begin using it for development tasks.
Step 1: Open your Salesforce org. From Setup, enter Development in the Quick Find box, and then select Web Console (Beta).
Step 2: Turn on the Enable Web Console (Beta) toggle by switching it to Active.
Step 3: Wait a few seconds for the changes to take effect. Once the gear menu is updated, you’ll see the Web Console (Beta) option available. Open it directly from the gear menu to start using the Web Console.
Another way to access the Web Console (Beta) is directly from Apex-related pages:
- From Setup, enter Apex Classes, Apex Triggers, or Apex Jobs in the Quick Find box.
- Open the respective page, and you’ll see a list of records (for example, Apex classes).
- Click the Edit link next to an object name, or select Web Console (Beta) to open and edit the object directly in the Web Console.
For instance, on the Apex Classes page, clicking the Edit link for a class will open it in the Web Console, allowing you to make changes instantly.
Navigate the Web Console (Beta) User Interface
The Web Console (Beta) interface is designed to provide a clean and efficient development experience. It is divided into five key sections, each serving a specific purpose to help you work seamlessly within your Salesforce org.
Activity Bar:
This vertical bar contains icons that allow you to switch between different views. By default, the Explorer view is active. Other available views include:
- Explorer – Displays your project files
- Search – Helps you find and replace text across files
- Source Control – Lets you manage Git repositories and track changes
- Run and Debug – Enables execution and debugging of code
- Extensions – Shows pre-installed extensions (custom installations from Marketplace aren’t supported)
- Org Browser – Allows you to explore metadata directly from your Salesforce org
Sidebar:
The sidebar changes based on the selected view in the Activity Bar. For example, in the Explorer view, it displays files organized in a DX project structure, making navigation simple and intuitive.
Editors:
This is the main workspace where you write and modify code. You can open multiple files at once and arrange them side by side, either vertically or horizontally, for better productivity.
Output Panel:
Located typically at the bottom, this panel displays logs, terminal output, and debug information in separate tabs. You can switch between tabs depending on what details you need to review.
Status Bar:
The status bar provides real-time information about your current project and the files you’re working on. It also indicates tracing details when debugging is enabled, helping you monitor activity efficiently.
Command Palette
The Command Palette is a powerful feature that gives you quick access to a wide range of Salesforce development commands directly within the Web Console (Beta).
To open the Command Palette:
- Press Ctrl + Shift + P on Windows or Linux
- Press ⇧⌘P on macOS
Once opened, you can search for specific commands related to Salesforce development. For example, entering keywords like SFDX will display relevant commands that you can execute instantly.
After running a command-whether it completes successfully, fails, or is canceled-you’ll receive feedback in the Output tab. This helps you track execution results and debug issues if needed.
For instance, when you run the SFDX: Create Apex Class command, the Output tab displays the execution details, confirming whether the class was created successfully or if any errors occurred.
Debug Your Code
The Web Console uses Salesforce debug logs to help developers monitor and troubleshoot code execution.
In the Web Console (Beta), debug logs are enabled by defining trace flags and log levels in the traceLogs.json file. This allows you to control what level of detail is captured during execution, making it easier to identify issues in your code.
To quickly set up tracing:
- Hover over the No Tracing label in the status bar
- Select Create trace flags for the current user
- This action adds a trace flag for your user, enabling log generation
Once enabled, you can execute your code and review detailed logs in the Output panel, helping you debug and troubleshoot more effectively.
Query Records
You can run SOQL queries directly in the Web Console (Beta) to fetch and analyze data from your org. This allows quick data checks and debugging without switching to other tools.
Build a Query Using SOQL Builder
The SOQL Builder in Web Console (Beta) provides a visual, form-based interface to create queries without writing SOQL manually. You can select objects, fields, and filters using UI elements, and the query is generated automatically.
Steps to use SOQL Builder:
- Open the Command Palette and run SFDX: Create Query in SOQL Builder.
- Enter a name for your query and press Enter.
- Use the interface to choose the object, fields, and conditions.
As you configure the query, the corresponding SOQL statement is generated in the query box, making it easy to understand and execute.
To execute your query in the SOQL Builder, click Run Query. The results are displayed in a grid format for easy viewing. You can also export the results as CSV or JSON by selecting the respective option in the results tab.
Retrieve Query Plans
The Query Plan tool helps developers understand how Salesforce processes a query.
To retrieve a query plan:
- Open your query in the SOQL Builder
- Click Get Query Plan
This helps you identify performance improvements and ensure your queries run efficiently.
Run Query from Text Editor
You can also execute SOQL queries directly from the text editor in the Web Console (Beta).
Steps:
- Select the query in the editor
- Open the Command Palette and run SFDX: Execute SOQL Query with Currently Selected Text
- Choose the appropriate option based on your use case:
- REST API – For data operations like querying or modifying records
- Tooling API – For metadata and development-related tasks
The results are displayed in the Output panel, and a CSV file is generated for download.
Work with Apex Code (Beta)
In Salesforce, Apex is primarily written and stored in two forms:
- Classes:
These act as blueprints for creating objects and contain methods, variables, and logic. You can manage them from Setup → Apex Classes. - Triggers:
These are pieces of code that run automatically before or after specific data operations (like insert, update, or delete). Triggers are stored as metadata and can be accessed from Setup → Apex Triggers.
Using the Web Console, you can easily create, edit, and manage both Apex classes and triggers directly within your org.
Follow these steps to create an Apex class in Web Console (Beta):
- Open the Command Palette.
- Search for and select SFDX: Create Apex Class.
- Select the template type.
- Enter a name for your class and press Enter.
- The class opens in the editor, where you can add your logic and save it directly in your org.
Create an Anonymous Apex Script
You can quickly execute Apex code without creating a class by using an anonymous script.
Steps:
- Open the Command Palette.
- Run SFDX: Create Anonymous Apex Script.
- Update the sample script in the editor with your code.
- Save the file (it is stored in the scripts folder).
This is useful for testing logic or running one-time operations directly in your org.
Execute an Anonymous Script
You can run your anonymous Apex script directly from the editor in the Web Console (Beta).
Steps:
- Ensure your script is open in the text editor
- To execute the entire script:
- Right-click in the editor and select SFDX: Execute Anonymous Apex with Currently Open Editor
- To execute specific code:
- Highlight the desired portion, right-click, and select SFDX: Execute Anonymous Apex with Editor’s Selected Text
This allows you to quickly test full scripts or specific logic as needed.
You can also execute these actions from the Command Palette while the script is open in the editor.
After execution, the results and debug logs are displayed in the Output panel, allowing you to review the outcome and troubleshoot if needed.
Retrieve and Manage Salesforce Metadata in Web Console (Beta)
Step 1: Click on the Salesforce Org Browser icon from the Activity Bar.
Step 2: Browse or search for the component you want to retrieve.
Step 3: You can retrieve metadata either in bulk or individually:
- To retrieve all Apex classes at once, click the Retrieve Metadata icon located in the top-right corner of the ApexClass section.
- To retrieve a specific class, click the Retrieve Metadata icon next to that particular class.
Conclusion
The Web Console (Beta) is a step forward in simplifying development inside Salesforce. By bringing development tools directly into the platform, it reduces the need for multiple applications and helps developers complete tasks more efficiently from a single workspace.
Whether you’re making quick code changes, testing business logic, analyzing data, or managing metadata, the Web Console provides a more streamlined way to work within your org. As Salesforce continues adding new capabilities, this browser-based tool can help teams save time, improve productivity, and make day-to-day development easier to manage.
Watch Live Demo
No Data Found.
India 
USA
UK
Canada