Salesforce Data Toolkit

A Salesforce toolkit for VS Code covering data export/import, record and metadata comparison across orgs, an Apex console, org health monitoring, and QA/release utilities — without leaving VS Code. Inspired by the "Data Export" and "Data Import" features of the Salesforce Inspector Advanced Chrome extension.

Requirements

• Salesforce CLI (sf) installed and at least one org authenticated (sf org login web). This extension reuses those authenticated sessions instead of asking you to log in again.

Features

Each feature below opens in its own tab of the same panel, or directly via its own Command Palette entry.

Export (SOQL)

1. Run SF Data Toolkit: Open Query Editor (Export) from the Command Palette.
2. Pick a Salesforce org (first time only, or click the org indicator to switch).
3. Write a SOQL query and click Run Query. Results (including flattened parent-relationship fields like Account.Name) render in a table — click any cell to copy its value.
4. Click Export to CSV to save the full result set to a file.

Queries are auto-paginated up to 50,000 records; a warning is shown if a query is capped. As you type, FROM/SELECT/WHERE/ORDER BY/GROUP BY/HAVING all suggest SObjects and fields (including relationship traversal, e.g. Account.Owner.Name). Click Query Plan to see each candidate plan's leading operation type and relative cost before running a query on a large object — a TableScan means no index is being used.

Any cell (or Debug Log row) containing a Salesforce record Id gets a small ↗ next to it that opens that record directly in the org's browser UI.

Import (CSV)

1. Right-click a .csv file in the Explorer and choose SF Data Toolkit: Import CSV Data (or run the command from the palette and choose a file from the Import tab).
2. Pick the target object and operation (Insert / Update / Upsert / Delete). Upsert requires an External ID field.
3. CSV columns are auto-matched to fields by name — adjust the mapping table if needed.
4. Click Start Import. The load runs via Bulk API 2.0. On completion you'll see a success/failure count; if any records failed, an error log CSV is written next to your source file.

Orchestration Monitor

Run SF Data Toolkit: Open Orchestration Monitor. Load one or more Order Management orchestration items by Order Id (single, pasted list, or a CSV column of Order Ids) and see each step's status, with failures and their error text highlighted.

Compare Records

Run SF Data Toolkit: Compare Two Records. Pick an object and two record Ids to diff every field side-by-side — matches show 👍, differences show 👎, with a summary badge and a jump-to-first-difference shortcut. Values are formatted by field type (booleans as ✓/✗, dates, currency). Check Compare across two orgs to look up the second record in a different authenticated org (e.g. sandbox vs. production) instead of the same one. Recent comparisons are remembered for one-click reload.

Metadata Diff (Two Orgs)

Run SF Data Toolkit: Open Metadata Diff (Two Orgs). Pick two orgs and an object to diff its field definitions (type, length, required, unique, picklist values, etc.) between them — useful for confirming a deploy landed the same way in both places, independent of any specific record's data.

Anonymous Apex Console

Run SF Data Toolkit: Open Anonymous Apex Console. Write and execute anonymous Apex against the selected org via the Tooling API, and see compile errors, exceptions, and captured System.debug() output (plus the full raw debug log). This sets up a temporary trace flag/debug level on your user to capture the log — the only feature in this extension that writes to org debugging configuration rather than just reading or exchanging data you asked for.

LWC Local Preview (No Deploy)

Open any file inside a component's lwc/<componentName>/ folder, then run SF Data Toolkit: Preview This LWC Component (Local Dev, No Deploy) from the palette, or right-click the file (Explorer or editor). This wraps Salesforce's own sf lightning dev component in a terminal, scoped to the component you had open and the currently selected org — it streams your local source into a live browser preview with hot reload on save, without a deploy. Requires Local Dev to be enabled on the target org (a scratch org, or a Dev/Enterprise-tier sandbox with the preference on) — if it's not enabled, the CLI's own error explains that directly in the terminal.

Debug Logs

Run SF Data Toolkit: Open Debug Logs to browse recent Apex debug logs from anyone in the org — not just this tool's own Apex Console runs. Click a log to see it colorized and collapsible (DML/SOQL/callouts/exceptions each get their own color, nested execution is an expandable tree) instead of a raw text dump, with the governor-limit usage from the end of the log parsed into a bar table up top. Click Enable Logging first if you need to capture a new run — this sets up the same temporary trace flag/debug level as the Apex Console.

Apex Test Runner

Run SF Data Toolkit: Open Apex Test Runner. The class list is built by scanning this workspace's **/classes/*.cls for @isTest — not an org query, since ApexClass.Body isn't filterable via SOQL — so open the SFDX project folder containing your classes first. Select the classes to run, click Run Selected Tests, and watch pass/fail per method with stack traces on failure. Refresh Coverage separately shows org-wide per-class code coverage (cumulative across all runs, not just the ones you just ran) with a usage bar, worst-covered first.

Org Limits Dashboard

Run SF Data Toolkit: Open Org Limits Dashboard for a snapshot of every org-wide limit (API calls, storage, etc.) with a usage bar, sorted by highest usage first.

Apex/Bulk Job Monitor

Run SF Data Toolkit: Open Apex/Bulk Job Monitor to see recent Apex jobs (batch/scheduled/queueable/future) and Bulk API 2.0 ingest jobs in one place, with failures highlighted.

Record Snapshot/Restore

Run SF Data Toolkit: Open Record Snapshot/Restore. Capture the current field values of specific records before a test run ("Take Snapshot"), then revert them afterward ("Restore Snapshot"). Only updateable fields are captured/restored; records created during the test aren't removed.

Duplicate Checker

Run SF Data Toolkit: Open Duplicate Checker. Pick an object and one or more fields (e.g. Email, or First+Last Name) to find exact-match duplicate groups (case-insensitive, whitespace-trimmed) — a simple, fast check for re-entry duplicates, not fuzzy/near-miss matching.

Field Dependency Viewer

Run SF Data Toolkit: Open Field Dependency Viewer to see what references a custom field (Flows, layouts, Apex, etc.) via the Tooling API's dependency graph, and what that field itself references. Only custom fields (ending in __c) are trackable this way — standard fields aren't covered by this API, and coverage otherwise varies by metadata type and org.

Field-Level Security Checker

Run SF Data Toolkit: Open Field-Level Security Checker. Pick a user, an object, and a field to see whether that user can effectively read/edit it, and which Profile or Permission Set grants (or would need to grant) that access — access is additive across everything a user has, so any single grant is enough. Required/always-visible fields (most commonly an object's own Name field) have no FLS entries at all; a note explains that rather than misreporting them as inaccessible.

Local vs Org Diff (Apex)

Run SF Data Toolkit: Open Local vs Org Diff (Apex). Compares every local Apex class/trigger (**/classes, **/triggers) against what's actually deployed in the connected org, flagging Drift (edited directly in Setup/Dev Console since your last pull), Local only (not deployed yet), and Org only (created directly in the org, missing from your local source) — before you deploy over any of it. Scoped to Apex classes and triggers for now; LWC/Aura bundles and other metadata types aren't covered yet.

Record Viewer/Editor

Run SF Data Toolkit: Open Record Viewer/Editor. Paste any record Id — the object type is resolved automatically from the Id's prefix, no need to pick it separately. Every field renders as a form row (checkboxes for booleans, dropdowns for picklists, text for everything else); read-only/system fields show up disabled rather than being hidden, so you can still see their current value. Edit whatever's editable and click Save Changes — it reloads the record afterward so you see the server-confirmed values (including any formula/rollup recalculation).

Custom Metadata Editor

Run SF Data Toolkit: Open Custom Metadata Editor. Pick a Custom Metadata Type to see every record as an editable spreadsheet-style grid — each row saves independently via the (SOAP-based) Metadata API, the only write path for __mdt records since the normal data/Bulk APIs can't touch them. Each save sends the record's full current field set (existing values merged with your edit), not just the changed field, since Salesforce's documented behavior for partial updates here is inconsistent — this avoids any risk of an omitted field getting silently cleared.

Deploy History

Run SF Data Toolkit: Open Deploy History. Recent Metadata API deployments in one list — CLI deploys included, since sf project deploy start creates the same DeployRequest record under the hood. Click a row with component errors to see the per-component failure detail (which file, which component, what the problem was), without re-running sf project deploy report.

Sandbox Refresh Tracker

Run SF Data Toolkit: Open Sandbox Refresh Tracker to see recent sandbox create/refresh jobs and their status. This data only exists in the production org — run this command from production, not from inside a sandbox (and it isn't available at all in Developer Edition orgs, which don't support sandboxes).

Org Health Digest

Run SF Data Toolkit: Open Org Health Digest for a one-glance ✅/⚠️ status combining limits at 70%+ usage and any recently failed Apex/Bulk jobs — a quick check before standup.

Release Readiness Checklist

Run SF Data Toolkit: Open Release Readiness Checklist for a pre-deploy sanity check: org-wide Apex test coverage, failing tests, failed background jobs, org limit headroom, and recent deployments. Each check is independent — if one of the underlying Tooling API objects isn't available in a given org, that item shows as informational instead of failing the whole checklist.

Development

npm install
npm run watch   # esbuild in watch mode

Press F5 in VS Code to launch an Extension Development Host with the extension loaded, then try the commands above.

Packaging

npx @vscode/vsce package