Data dictionary
Browse, search, and export every object and field in your Salesforce org.
The data dictionary is a live, searchable view of your org's schema. Every object and field is documented automatically from your metadata — nothing to write by hand, and it stays current as your org changes.
Built from metadata
The dictionary describes your org's structure — objects, fields, relationships, and their configuration. It never reads, stores, or shows record data.
Objects
The Objects list shows every object in your org and is searchable. Custom and standard objects are distinguished, so you can quickly narrow to the ones you maintain — for example, jumping straight to your custom Account.Industry__c-style fields by starting at their parent object.
Inside an object
Open any object to see its full definition, organized into tabs:
Every field on the object, with its type and configuration.
What breaks if you change or delete the object — the automations, layouts, and other components that depend on it.
What the object looks up to, and what references it back.
Record types defined on the object.
The rules that gate writes to the object.
Page layouts defined for the object.
Flows and Apex triggers that run on the object — definitions only, never the records they touch.
Schema changes recorded for this object over time.
The Change history tab ties the dictionary to change tracking: you can see an object's current definition and how it got there from the same place.
Ask about this object
From any object you can Ask about this object to open the assistant already scoped to it — useful for "what changed here lately?" or "which fields are barely used?" without leaving the page.
Inside a field
Open any field to see its complete definition:
| Attribute | What it shows |
|---|---|
| Data type | The field's type |
| Flags | Whether the field is required, unique, an external ID, or calculated |
| Governance | A badge when the field looks like it holds personal data — see PII detection |
| Population % | How often the field is filled in — see field usage |
| Impact | What would break if you changed or deleted the field — see impact analysis |
| Field-level security | Who can see and edit the field, by profile and permission set — see permissions |
| Description | The field's description |
| Help text | The field's help text |
| Field meaning | Its purpose, synonyms, and category |
| Picklist values | The values available on a picklist field |
| Value set | The value set a picklist draws from — see value sets |
| Change history | How the field's definition has changed over time — see change tracking |
Description and help text
A field's description and help text are synced from Salesforce as-is. Where a field has none, SchemaForce can draft one for you — those AI-authored descriptions are clearly marked, and you can optionally push an accepted draft back to Salesforce one field at a time. See AI documentation & Push to Salesforce.
Governance badges are a heuristic
A Governance badge flags fields that look like they hold personal data — it's a signal to review, not a compliance verdict. PII detection explains what it checks and what it deliberately doesn't.
Search
Global search spans both objects and fields, so you can jump straight to what you need without knowing where it lives. Type part of a label or API name and go directly to the matching object or field.
Two different searches
The dictionary search above finds objects and fields. The command palette (⌘K / Ctrl-K) is a separate, keyboard-driven way to jump to any object or page from anywhere in the app.
Value Sets
The Value Sets page lists global and standard picklist value sets, along with which fields use each one. This is useful for understanding shared picklists across the org — when several fields draw from the same value set, you can see them all in one place before changing it.
Export
Any dictionary table can be exported, so the documentation doesn't have to live only in SchemaForce.
Export to CSV for spreadsheets, audits, or sharing a snapshot with colleagues.