Object Overview reconstructs the full picture of any Salesforce custom object — its purpose, lifecycle, field inventory, and how it connects to the rest of the data model — without you having to manually piece it together from Setup screens. Use it when you inherit an unfamiliar object, need to explain a client's data model to a stakeholder, or want to produce clean post-engagement documentation.

Select a connected org, pick a custom object by API name, and dx0 queries its full metadata — fields, picklists, validation rules, record types, relationships, and recent record volume — then passes it to an AI model that produces a structured analysis. The result loads in the Summary tab.

This is the most valuable part of the output. Rather than listing field types in isolation, the AI synthesises picklist stages, date fields, checkboxes, and validation rules into a narrative that tells you how a record actually moves through the system.

If the object has three or more stages, branching paths, or gating conditions, the analysis opens with a Mermaid flowchart — a state-machine diagram showing the stages as nodes, transitions as edges, and hard gates as decision diamonds. Copy the analysis output and paste it into a Mermaid renderer (or directly into Notion, Confluence, or any tool that renders Mermaid) to get a lifecycle diagram ready to drop into a client deliverable.

A simple linear object (three or fewer stages, no branches) gets a prose description with inline arrows instead.

This section maps how the object fits into the broader data model. If there are two or more meaningful relationships, the analysis includes a Mermaid ER diagram with relationship labels that convey intent — "owns", "notifies", "expands into" — rather than just "Lookup" or "Master-Detail". The prose beneath it interprets what those relationships reveal: a Master-Detail to Sprint__c means records are deleted with their sprint; a Lookup to Case means an optional association with support tickets.

Two or three sentences establishing what the object is and what business function it serves. For custom objects, this includes a duplicate standard object check: dx0 recognises when a client has re-built a standard Salesforce object — Opportunity, Case, Lead, etc. — under a custom name, including translated names (Oportunidad, Cas, Opportunité, Pedido, and so on). This pattern is almost always a license cost workaround, and the analysis flags it as a critical finding if detected, including the specific downstream consequences.

Observations worth raising: inactive validation rules, picklist values that break the lifecycle pattern, checkboxes that suggest workarounds, design decisions that look like organic growth rather than intent. If nothing stands out, the section says so.

The Fields tab gives you the complete field inventory — label, API name, type, description, and help text — in a searchable, sortable table. Useful when you need to verify a specific field exists, check what type it is, or export a field list for documentation.

The Relationships tab shows parent and child relationships separately: direction, relationship type (Lookup vs Master-Detail), the related object, and the field that creates the link. This is a faster way to understand the object's structural dependencies than navigating Setup.

The copy button at the top-right of the Summary tab copies the full analysis as markdown. This is the fastest path to client-ready documentation — paste it into your report template, strip the sections you don't need, and edit from there. The ER and lifecycle diagrams copy as raw Mermaid code blocks, which renders natively in Notion, Confluence, GitHub, and most modern documentation tools.

The analysis is generated fresh each time you run it. If the org's metadata has changed, re-run to get an updated result.

Walking into an unknown org. A client says "we use Ticket__c for our support process" but hasn't documented it. Run Object Overview, read the lifecycle section, and you'll understand the stage model, the gating rules, and how it relates to Account and Contact before you've opened a single record.

Explaining a complex object to stakeholders. The Mermaid lifecycle diagram is presentation-ready. Copy, paste into Confluence or Notion, and you have a process map that would otherwise take an hour to draw manually.

Spotting a re-built standard object. A client is missing out on standard Case features — email-to-case, escalation rules, standard reports — because they built their own case management object three years ago. The duplicate object detection flags this, names the consequences, and gives you the framing for a migration conversation.

Post-engagement documentation. At the end of a project, run Object Overview on every custom object you touched. Copy the summaries into your handover document. Clients consistently cite this as one of the most useful things a departing consultant leaves behind.

Onboarding a new team member. Brief someone on a specific part of the data model by running Object Overview on the relevant objects and sharing the results. They get the lifecycle, the relationships, and the field inventory in one place, without needing a walkthrough from you.