Asset Relationship is a standard object that ships available in most Salesforce editions. The work is enabling it on the right page layouts, designing the Relationship Type picklist, and training users on the containment-versus-peer distinction.
- Confirm Asset Relationship is enabled
Setup, Asset Settings (or Object Manager, Asset Relationship). Confirm the object is enabled in the org. Most editions include it.
- Design the Relationship Type picklist
Configure the Relationship Type picklist with the values your org needs (Wired To, Networked With, Replaced By, Adjacent To). Keep the list short; large picklists turn the data into noise.
- Add Asset Relationship related lists to layouts
Drop the Asset Relationship related list on both Asset and Related Asset page layouts so users see peers from either side of the relationship.
- Train users on containment versus peer association
Establish a simple rule: contained components use Asset Hierarchy ParentId; peer associations use Asset Relationship. Without the distinction, data drifts.
- Build the report type
Create a custom report type Asset, Asset Relationship, Related Asset so reports can walk peer-to-peer associations.
- Asset Relationship is for peer association, not containment. Use Asset Hierarchy ParentId for containment; mixing them produces noisy data.
- Sharing is inherited from both endpoints. Users with access to only one Asset cannot see the relationship.
- Stale relationships are invisible without an End Date convention. Train users to End Date relationships when they are no longer current.
- Wide Relationship Type picklists dilute reporting. Cap the list at 8 to 10 values; extend only when reporting demands it.