Sales Grid

A VS Code extension for Salesforce developers. It lists every org you are connected to, opens any of them in the browser, and tells you whether the file you are editing matches the org and who last changed it there.

Requirements

• VS Code 1.85 or later
• Salesforce CLI (sf) on your PATH, with at least one authorized org (sf org login web)

Connected Orgs

Click the Sales Grid icon in the Activity Bar. The Connected Orgs view shows each org by alias, with its username, type and days left before it expires.

Keeps itself up to date. The list reloads by itself when you log in to or out of an org, change an alias or change the default org anywhere, including in a terminal, and after any Sales Grid action that changes an org. It also reloads when you come back to VS Code after ten minutes or more, since an org's connection can expire in the meantime.

Order. Pinned orgs come first. Orgs that are expired or cannot be reached are always listed last.

Icons. A star marks a pinned org, a cloud a connected org, a watch an org that expires soon, and a warning triangle an org whose login has expired or cannot be reached.

Production. Production orgs are shown in red with a P badge so they are hard to open by mistake. An org counts as production when the CLI reports an edition other than Developer Edition and it is not a sandbox, scratch org or trial. You can override the colour of any org with Set Colour Label....

Expiry. Scratch orgs and trial orgs show the days they have left. You get one warning per session for each org that expires within salesgrid.expiryWarningDays days.

Log In Again. Runs sf org login web for that org in a terminal and tells you whether the login finished. The same button is offered when opening an org fails because its session has expired. Expired scratch orgs cannot be logged in to again.

Remove Org. Only offered for orgs that are expired or cannot be reached, and always asks for confirmation first. It deletes the saved login from your computer (sf org logout); the org itself is not changed.

The file you are editing

When you open an Apex class, Apex trigger, Visualforce page or component, Lightning web component, Aura component or Flow, Sales Grid looks it up in your org and shows the result in three places: as links above the first line of the file, in the Current File view in the Sales Grid panel, and in the status bar at the bottom of the window. A spinner is shown in each while the org is being asked. Nothing has to be opened first; the details appear as soon as the file does.

Status bar. Shows Open in Salesforce, the active state, org test coverage, Created by and Last modified by with date and time for the current component. These sit to the right of other extensions' status bar items. Click the first to open the component in the org, or a name to open that user in Setup.

Toolbar icons. At the top right of the editor, the arrow icon opens the current file in Salesforce, and the Sales Grid icon opens the Sales Grid panel on the Current File details. Open Current File in Salesforce is also on the right-click menu of the editor and the Explorer.

Switching away. When you move to something that is not a file, such as a chat panel, the details of the last component stay on screen.

Activate or deactivate. Click Active or Inactive on a trigger or flow, in any of the three places, to switch it. You are always asked to confirm first, and the new state is shown everywhere as soon as the org reports it. For a flow, activating makes the latest version active. For a trigger, Salesforce only allows the change through a deployment: Sales Grid redeploys the trigger with the code already in the org, so local edits are not sent, and then sets <status> in the local .trigger-meta.xml to match. In a production org that deployment runs the Apex tests first.

If the saved file is different from the org, you also get a warning with a Compare button, once per file for each version in the org.

Code is compared for Apex classes, Apex triggers, Visualforce pages and components, and each file of a Lightning web component. Aura components, Flows and -meta.xml files show who created and changed them but are not compared.

Which org. The project's default org is used (sf config set target-org). If there is none and you have several orgs, click the cloud icon on the Current File view to choose one; the choice is remembered for the workspace.

After a deploy. The details update by themselves. Sales Grid asks the org when the open component was last modified every salesgrid.autoRefreshSeconds seconds while the window is in use, a few seconds after each save, and whenever you come back to the window. If that time has moved, the details, comparison and coverage are re-read. To force it, use the refresh icon on the Current File view.

Messages

Every action shows a notification saying whether it worked. On failure the notification gives the reason with Retry and Show Log buttons; the full history is in the Sales Grid output channel.

A copied open URL signs in to the org without a password and stays valid for a short time. Treat it like a credential.

Configuration

Everything is set on one page. Open it with the gear icon on either Sales Grid view, or press Ctrl+Shift+P and run Sales Grid: Open Configuration. It is the only Sales Grid command in the Command Palette; every other action is a button, a link or a right-click entry. Changes are saved and applied as you make them.

Where details are shown

A grid of tick boxes: one row per detail, one column per place.

The values above are the defaults. The first row of the page switches the whole footer, or everything inside the file, on or off.

Features

• Activate / deactivate: switch a trigger or flow on or off by clicking its status. When off, the status is still shown but cannot be clicked.
• Mismatch warning: the warning shown when a file you open is different from the org.
• Editor toolbar buttons: the Open in Salesforce and Sales Grid buttons at the top right of the editor.
• Right-click menu entries: Open in Salesforce and Compare with Org on the editor and Explorer menus.

General

• Expiry warning (days): warn when a scratch or trial org expires within this many days. Defaults to 7.
• Auto refresh (seconds): how often to ask the org whether the open component changed. Each check is one API call. Defaults to 30; 0 turns it off.
• Salesforce CLI: command or full path for the CLI. Defaults to sf.

The same options are also listed under Sales Grid in the VS Code Settings editor, with names starting salesgrid..

Running it from source

Try it without installing: open this folder in VS Code and press F5. A second VS Code window opens with the extension loaded.

Build and install:

npx @vscode/vsce package
code --install-extension sales-grid-0.1.3.vsix

Files

• package.json: extension manifest (views, commands, menus, settings)
• extension.js: views, commands and notifications
• sfCli.js: wrapper around the Salesforce CLI
• component.js: maps a source file to its Salesforce component and Setup page
• configPage.js: the configuration page
• resources/icon.png: extension icon (full colour)
• resources/activitybar.png: Activity Bar icon (single-colour version of the logo mark)
• resources/toolbar.png: editor toolbar icon (full-colour logo mark)