A growing set of Salesforce DX tools inside VS Code by SFDXLabs.com. Version 1.9.8 adds mixed custom/standard schema selection and incremental object loading.
Flow and Automation
Open SFDXLabs Salesforce Toolkit → Automation to:
- Visualize local
.flow-meta.xml files as connected element graphs using their Flow Builder coordinates when available
- Drag elements into clearer positions while their connectors and path labels remain attached, or use the arrow keys for precise movement
- Jump from lint findings directly to the relevant Flow metadata line
- Detect missing fault connectors, DML or Get Records inside loops, hard-coded Salesforce IDs, same-object after-save update risks, unreachable elements, missing descriptions, and inactive Flows
- Build an object-level map of validation rules, before-save Flows, Apex triggers, after-save Flows, legacy workflow rules, and scheduled/asynchronous automation
- Review inactive local Flow files and move selected metadata to the operating-system Trash
- Query inactive org Flow versions through the Tooling API and permanently delete only explicitly selected versions after typing a generated confirmation phrase
Flow lint and automation-map JSON reports are written beneath data-dictionary/automation/. The order-of-execution map is deliberately labelled approximate because entry criteria, recursion, managed packages, and org-only automation can affect runtime behavior.
Advanced Data Operations
Open SFDXLabs Salesforce Toolkit → Data to:
- Export parent/child SOQL results as Salesforce sObject tree files and an ordered import plan
- Import a tree plan or explicitly ordered JSON files after a modal target-org confirmation
- Save reusable sandbox seed recipes and run them from a source org into an optionally selected target org
- Query up to 2,000 records and replace selected string, textarea, email, phone, URL, and encrypted-string fields with deterministic anonymous values
- Resume import, update, upsert, or delete Bulk API jobs and retrieve their completed result CSV files
Salesforce tree export is limited by the Composite API to 2,000 records. Seed recipe runs use a new timestamped output directory so earlier plans cannot be imported accidentally. Anonymized exports retain Salesforce record IDs for correlation and should still be handled as controlled project data.
SOQL and Record Workspace
Load the objects you want in the Schema Explorer, then open SFDXLabs Salesforce Toolkit → Data → SOQL & Record Workspace. You can:
- Use a compact, capped-width builder rail while the active query and editable rows take the remaining window width
- Keep multiple UI Builder and free-form query tabs open, renamed, saved, and restored independently
- Edit free-form SOQL and Builder
WHERE expressions with live syntax highlighting; generated active queries are highlighted too
- Choose visible columns using object and field labels or API names
- Filter with a
WHERE expression, choose ASC or DESC ordering, and optionally omit LIMIT
- Edit fields that Salesforce marks as updateable, including booleans and picklists
- Review highlighted changed cells before explicitly confirming an org update
- Export all rows or selected rows as CSV, JSON, or Excel-compatible SpreadsheetML
- Copy selected rows as tab-separated data with column headings
Inline edits are enabled only when a query returns one loaded object and includes record IDs. Updates are validated against the displayed result set and grouped into one Salesforce operation per record. The former Record Browser command opens this merged workspace, and its saved builder configuration is migrated when possible. Tabular exports flatten relationship fields into columns such as Account.Name; JSON preserves the original nested result structure.
Debug Studio
Open SFDXLabs Salesforce Toolkit → Debug to:
- Run selected Apex test classes, one or more Apex test suites, or all local tests
- Review passed, failed, and skipped methods in the Apex Test Dashboard
- Rerun every class that failed in the last run
- Jump from a test or coverage row to the matching local
.cls source file
- Inspect per-class uncovered lines and test-run coverage
- Select from the 100 most recent org debug logs
- Review SOQL, DML, callout, validation, Flow, exception, and user-debug events in a structured timeline
- See governor-limit usage ranked by percentage consumed
- Write and run Anonymous Apex in persistent, renameable tabs with independent results
- Edit Apex with live, VS Code theme-aware syntax highlighting in every tab
- Save and load
.apex scripts from any tab; existing single-editor drafts migrate automatically
Test reports, raw logs, and parsed log analyses are kept in private VS Code extension storage by default. Set sfdxlabs-tool-kit.debugOutputLocation to project only when you intentionally want them beneath data-dictionary/debug/.
Impact analysis
Right-click a loaded object or field and choose Find Where Used or Run Safe Delete Check. The toolkit scans local Apex, LWC, Aura, Flow, validation rule, layout, object, and permission metadata, then combines those results with formulas and relationships in the loaded org schema. Results link back to source lines and are saved as JSON evidence reports.
The Schema view also includes Run Data Quality Audit, which can report missing descriptions and help text, empty picklists, missing relationship names, and duplicate field labels. Choose exactly which checks to include each time; the selection is remembered for the workspace.
The Security sidebar now provides:
- Permission Matrix — compare object CRUD and field access across local profiles and permission sets
- Compare Permissions — detailed differences between two local permission sources
- Explain User Access — select an active org user, object, and optional field to trace effective CRUD/FLS grants back to the profile or permission set that grants them
Security and impact reports are written beneath data-dictionary/analysis/.
SOQL & Record Workspace
Load a schema, then open Data → SOQL & Record Workspace. The workspace supports:
- Multiple query tabs with independent state and results
- Renameable and closeable tabs
- UI Builder or free-form SOQL mode per tab
- Builder → Free-form copies the generated query; Free-form → Builder warns before discarding free-form text
- Object and field selection without losing choices while filtering
- Optional
WHERE and LIMIT clauses plus explicit ASC/DESC ordering in Builder mode
- Copy, editor insertion, execution, and in-panel results
- Selected-row copying and CSV, JSON, or Excel-compatible result exports
- Saving the active query as a
.soql file
- Loading
.soql or text queries into new free-form tabs
- Automatic restoration of tabs for each workspace and target org
- Guarded inline editing for direct fields when the result includes
Id
- Stale-result protection, grouped record updates, and explicit write confirmation
Schema Explorer
Open the SFDXLabs Salesforce Toolkit activity-bar view and choose Load Org Schema. After selecting an authenticated org and object set, you can:
- Start with Primary custom objects to omit generated
__Share, __History, and __ChangeEvent objects, or explicitly choose a broader scope when needed
- Start with every primary custom object and then manually select only the standard objects you need
- Add one or more objects to an already loaded schema set without reloading its existing objects
- Browse objects and fields in a lazy, searchable tree
- Expand the collapsed object/field summary only when you need the full tree
- Filter custom, required, formula, relationship, external ID, and picklist fields
- Open rich object and field detail panels
- Copy API names and starter SOQL
- Export the currently loaded schema directly to CSV, JSON, and Markdown
- Jump directly to local object or field metadata XML
- Visualize relationships between the loaded objects
- Refresh the loaded schema without using cached responses
Snapshots and comparisons
The Schema view can save named snapshots and compare:
- Two saved schema snapshots
- Two authenticated Salesforce orgs
- Local Salesforce metadata against the currently loaded org
Every comparison opens an interactive change report and writes deterministic JSON, Markdown, and CSV reports beneath data-dictionary/schema-comparisons/. Saved snapshots are stored beneath data-dictionary/schema-snapshots/.
Data dictionary
The dictionary connects through the installed sf CLI and exports object and field metadata visible to the selected authenticated org user.
Included metadata covers:
- Object and field labels, API names, and descriptions
- Field types, sizes, precision, scale, and SOAP types
- Required, unique, external ID, encrypted, and auto-number flags
- Formulas, default values, and default formulas
- Relationships and controlling fields
- Active, inactive, default, dependent, and restricted picklist information
- Query, create, update, delete, filter, sort, and group capabilities
By default it creates deterministic files that are easy to review in Git:
data-dictionary/salesforce-data-dictionary.csvdata-dictionary/salesforce-data-dictionary.jsondata-dictionary/salesforce-data-dictionary.md
Requirements
- Visual Studio Code 1.90 or later
- Salesforce CLI (
sf) installed and available on the VS Code extension host PATH, or configured with SFDXLabs Salesforce Toolkit: Salesforce CLI Path
- At least one authorised Salesforce org
- A Salesforce DX project containing
sfdx-project.json
Use
- Open a Salesforce DX project in a trusted VS Code workspace.
- Open the SFDXLabs Salesforce Toolkit activity-bar view or the Command Palette.
- Run SFDXLabs Salesforce Toolkit: Generate Data Dictionary.
- Select an authenticated org.
- Select primary custom objects (recommended), all custom objects, standard objects, all accessible objects, or individual objects.
- The configured exports are generated and the preferred file opens automatically.
The extension supports multi-root workspaces and nested Salesforce projects. Long-running CLI processes can be cancelled from the progress notification.
If sf works in the integrated terminal but the extension cannot find it, open VS Code Settings, search for SFDXLabs Salesforce Toolkit: Salesforce CLI Path, and enter the full path returned by command -v sf (macOS/Linux) or (Get-Command sf).Source (PowerShell). Leave the setting blank to use normal PATH discovery.
The SFDXLabs Salesforce Toolkit activity-bar container uses one compact tree, avoiding the large empty gaps that VS Code reserves between separate view panes. Its collapsible sections are:
- Schema — interactive schema exploration, relationships, snapshots, comparisons, and dictionary generation
- Security — permission matrices, source comparison, and effective user access
- Deploy — reserved for package, validation, and org-drift tools
- Debug — Apex tests, coverage, debug logs, governor limits, and Anonymous Apex
- Data — unified SOQL/record workspace, relationship datasets, seed recipes, anonymization, and Bulk API jobs
- Automation — Flow visualization, linting, object automation maps, and inactive-version cleanup
Actions are grouped by task and longer explanations are available as hover tooltips instead of clipped inline text. The skipped Deployment Workbench is kept collapsed as Deploy (Roadmap); its design and the complete release plan are documented in ROADMAP.md.
Settings
sfdxlabs-tool-kit.salesforceCLIPath: Optional full path to the Salesforce CLI executable; leave blank to use the extension host PATH.sfdxlabs-tool-kit.outputDirectory: Output directory inside the Salesforce project.sfdxlabs-tool-kit.apiVersion: Optional API version override.sfdxlabs-tool-kit.outputFormats: Any combination of csv, json, and markdown.sfdxlabs-tool-kit.useTimestamps: Generate timestamped snapshots instead of stable filenames.sfdxlabs-tool-kit.concurrency: Maximum simultaneous object describe requests, from 1 to 10; description enrichment is loaded in bounded batches.sfdxlabs-tool-kit.cacheTtlMinutes: Persistent schema-cache lifetime; set to 0 to bypass reads.sfdxlabs-tool-kit.debugOutputLocation: Keep sensitive debug artifacts in extension storage (default) or write them into the project.
Use SFDXLabs Salesforce Toolkit: Clear Schema Cache whenever you need to force a complete refresh.
Development
npm ci
npm test
npm run package
The implementation is separated into command orchestration, Salesforce CLI access, schema loading and caching, exporters, and VS Code UI modules.
| |
