Salesforce Metadata Inventory
Build a custom-first inventory of Salesforce components, filtering out standard and package clutter.
Definition
Salesforce Metadata Inventory refers to the complete cataloging of customized configurations within an org. This includes code (Apex, LWC), automations (Flows, Triggers), data structure (Custom Fields, Custom Objects), and security settings, structured for architectural review.
Overview & Context
Standard Salesforce orgs contain thousands of default components and objects. Finding custom code and configurations within this noise is a major challenge for developers. SF Analyzer implements a custom-first retrieve filter that separates managed package assets and default Salesforce types from your unique codebase.
Important Architecture Notice
SF Analyzer strictly enforces the local data boundary. Your Salesforce metadata, credentials, and source files never leave your system.
TL;DR (Too Long; Didn't Read)
SF Analyzer maps all metadata components in your org, distinguishing custom development from standard Salesforce boilerplate and managed packages.
Key Advantages
- Noise-FilteringExcludes standard namespace objects and third-party package clutter by default.
- Registry-SafeValidates types against local CLI registries to prevent retrieval crashes.
- Git IntegrationTracks changes in a local git repository to show changes over time.
Typical Use Case
Used by development teams preparing for a transition to Salesforce DX (scratch orgs), identifying orphan custom fields, or cataloging legacy metadata components for cleanup.
Analysis Workflow
Run describe metadata types to build the complete Salesforce metadata registry.
Apply custom-first filters to isolate objects and fields built by your team (excluding standard and managed packages).
Enumerate custom Apex, Triggers, Flows, LWC, Aura components, and custom fields.
Store the resulting structured inventory locally, ready for analysis and version tracking.
How It Compares
Compare the secure local-first workflow against traditional cloud-based SaaS vendors.
| Feature | Standard sfdx-project | SF Analyzer Catalog |
|---|---|---|
| Standard Boilerplate | Retrieved and mixed into project folders | Filtered out to focus on custom configurations |
| Namespace Separation | Manual exclusion required in package.xml | Automatic isolation of namespace prefixes |
| Local History | Requires manual git setup and commits | Automated local git commits per analysis run |
| Dependency Mapping | Not provided without manual toolsets | Built-in dependency links parsed from snapshot metadata |
Frequently Asked Questions
Find answers to technical and operational questions about Salesforce Metadata Inventory.
Q:Can I include standard objects if I have customized them?
Yes. SF Analyzer's custom-first filter selectively includes standard objects only if they contain custom fields, custom validation rules, or custom buttons, preserving your actual business logic while ignoring standard fields.
Q:What metadata types are supported by the retrieve catalog?
SF Analyzer supports over 280 metadata types registered in the Salesforce metadata API, including CustomObjects, ApexClasses, ApexTriggers, Flow, LightningComponentBundles, and Security configurations.
Ready to assess your Salesforce Org?
Download the SF Analyzer desktop application. Connect your sandbox or production org via the CLI, and run the assessment 100% locally.