Swantide's Data Dictionary lets you export your metadata inventory, or any filtered subset, as a CSV. Use this for offline analysis, sharing with stakeholders who don't have Swantide access, or consolidating data in Excel or Google Sheets.
When to use this
You need a comprehensive list of all fields, flows, Apex classes, or other metadata in your org.
You want to share documentation with a team member or client who doesn't have Swantide access.
You're building a cleanup plan and need to sort and filter in a spreadsheet.
You're consolidating metadata across component types for an audit.
Step-by-step
Open the Data Dictionary in your connected org.
Filter and/or search: the export respects whatever view you're currently looking at. Narrow to the category or search term you need.
Click the Download CSV button: Swantide kicks off the export. The file lands on your Artifacts page when ready.
Open in Excel or Google Sheets for offline analysis.
What's in the export
Each row corresponds to one metadata component in your filtered view. The columns shown in the Data Dictionary table are Component, Type, and Documentation:
Column | Description |
Component | The component's label / name |
Type | The metadata type (e.g., |
Documentation | Swantide's AI-generated description |
The exact column set may vary slightly by component type and product updates, so open the export and check the header row to confirm what's included.
Pair the export with the AI Assistant
The CSV gives you a complete, deterministic list of what exists. One thing to know before you count rows: Salesforce files standard objects and fields under the same CustomObject and CustomField types as your custom ones, so those totals cover everything in the org rather than only your customisations. Filter to names ending in __c when you want the custom footprint on its own. The AI Assistant gives you analysis on top of a focused subset. Common follow-up prompts after an export:
"Here's a CSV of all custom fields on the Account object. Which of these look like duplicates or candidates for consolidation?"
"I exported all flows in this org. Group them by object and tell me which ones overlap in trigger criteria."
"From the attached CSV of validation rules on `Opportunity`, summarize which ones fire on stage transitions and which fire on field changes."
For broad reference tracing across the whole org, use the References tab on each component rather than asking the AI Assistant to scan an export of everything.
Tips
Filter before exporting. Large orgs can have tens of thousands of components, so narrow first, then export.
Exports land in Artifacts. Look for them on the Artifacts page; you can re-download from there.
Combine with References. Open the CSV in Excel and pivot to map dependencies across your org.
Sharing with clients. Export the relevant component types and attach the CSV to your project documentation.