When to perform this analysis?
Run this analysis during:
Initial Org Discovery: To understand critical objects before proposing solutions.
Pre-implementation Assessment: When evaluating scope and risk of a change project.
Post-Acquisition/Org Merge Reviews: To identify hotspots in inherited orgs.
Audit or Technical Debt Reviews: To detect over-customization or fragile configurations.
Avoid using this analysis in:
Org models without automation (e.g., sandbox shells).
Early-stage orgs with minimal metadata and configuration.
Prerequisites
A connected and synced Salesforce Metadata Dictionary.
Required Elements.cloud permissions:
Org model viewer: View results and share dashboards.
Org model editor: Run and save queries.
Org model manager: Delete saved queries.
Perform Org Discovery via Object Automation Analysis
Step 1: Navigate to the Object Analysis Dashboard
Open your Metadata Dictionary.
Click the Analytics 360 button in the top-right.
In the left-hand menu, expand Objects and select Object Analysis.
Step 2: Start a New Analysis
In the dashboard, go to the Home tab.
Click New Analysis (top right).
Under "What kind of object insights are you looking for?", select Automations only.
Step 3: Define Analysis Criteria
In Object selection mode, choose:
Filter by categories to analyze object groups - recommended.
Or Select objects to analyze specific known objects.
Use filters to refine scope:
Automation Type (e.g., Apex, Flows).
Automation Attributes (include inactive and/or managed).
Save criteria if needed using Save Analysis before running.
Step 4: Run the Analysis
Click Run Analysis (bottom right). A stacked bar chart appears:
Each bar = a Salesforce object.
Each stack = a metadata type tied to the object.
Colors = types (Flows, Apex, etc.).
Step 5: Interpret Results
Hover the object name to see a count summary for all present object dependencies with split into metadata types, over stacks for the count of individual metadata types.
Click bar (object name): View all contributing components in an actionable list.
Click stack (e.g., Apex section): See filtered component list.
Use the right-side legend and metadata type dropdown to fine-tune your view.
Step 6: Drill Down into Metadata Lists
From the list view, explore:
Attributes of components.
Bulk actions: Tag, assess, document, create stories, or analyze dependencies.
Sort & filter to find automation hotspots or inactive/managed items.
Step 7: Use Output for Risk & Impact Assessment
Objects with:
High counts of automations
Multiple types (Flows, Apex, PB)
High configuration depth
...indicate importance and risk. Flag these for further investigation before proposing changes; you can use MetaFields.
Key Benefits
Accelerate Org Discovery: Surface high-importance objects in minutes.
Quantify Risk: Object complexity and automation depth visualized clearly.
Informed Planning: Prioritize testing and stakeholder involvement around risky areas.
Efficient Audit Trail: Drill directly to automation components for documentation and traceability.
Important Considerations
Custom Settings are treated as custom objects.
Automation Type Nuance: “Process Builder” and “Workflow Rule” are separate types.
Dependency Logic: “Automations only” also includes automations affecting dependent metadata (e.g., triggers writing into object fields).