What is the most important tip for working with Asset Relationship?

Use Asset Hierarchy for containment and Asset Relationship for peer association. The distinction is foundational; collapsing it makes reports unusable.

Core CRMBeginner

Asset Relationship

Q: How does Asset Relationship differ from Asset Hierarchy?

Asset Hierarchy is strictly parent-child, while Asset Relationship supports typed, directional links like 'is compatible with' or 'depends on'.

Q: What fields define an Asset Relationship record?

An Asset Relationship links two Assets with a From, To, and a Relationship Type that describes the nature of the link.

Q: Why would you use Asset Relationships instead of parent-child hierarchy?

Asset Relationships are the right tool when the real-world connections between Assets aren't strictly parent-child, like cross-system dependencies or compatibility links.

Asset Relationship is the Salesforce standard object that stores non-hierarchical associations between two Assets.

Hear it

§ 01

Definition

Asset Relationship is the Salesforce standard object that stores non-hierarchical associations between two Assets. Where Asset Hierarchy uses the ParentId field to model containment (this component is inside this installation), Asset Relationship models peer connections (this router is wired to this modem, this engine sits next to this generator). The object has fields for the two Assets, a Relationship Type picklist (Wired To, Networked With, Replaced, Bundled With), a Begin Date, an End Date, and any custom fields the org adds. Asset Relationships are queryable, reportable, and editable from a related list on either side of the relationship.

Asset Relationship is most useful in Field Service, IoT, telecommunications, and any business that services connected equipment. The object answers questions Asset Hierarchy cannot: which other devices share a circuit with this faulty one, which adjacent assets need testing after a replacement, which warranty contracts cover both assets together. Salesforce ships standard Asset Relationship records on the platform; Industries solutions and Field Service extend the schema with industry-specific Relationship Types and dashboards. Most production rollouts of Asset Relationship pair it explicitly with Asset Hierarchy so containment and peer association are modelled cleanly and reports do not conflate the two.

§ 02

How Asset Relationship complements Asset Hierarchy

The data model

Asset Relationship has two lookup fields, AssetId and RelatedAssetId, plus Relationship Type and date fields. Each row represents one peer relationship. The object is bidirectional in the sense that Asset A linked to Asset B implies B is linked to A, though Salesforce stores the row once and exposes it through related lists on both sides.

Relationship Types

The Relationship Type picklist drives meaning. Standard values include Wired To, Networked With, Replaced By, Bundled With. Admins extend the picklist for industry-specific cases (Backup For, Adjacent To, Co-Located With). The type is what makes reports useful; without a clear taxonomy, related Assets become noise.

Date fields and lifecycle

Begin Date and End Date let the relationship be time-bound. A modem replaced by a newer model can have the old relationship End Dated and the new one Begin Dated, preserving history. Field Service Service Appointment routing can filter active relationships to find only currently-relevant peers.

Containment versus peer association

Asset Hierarchy is containment (ParentId). Asset Relationship is peer association. The distinction matters because reports rolling up children give different answers than reports walking peers. A common mistake is using Asset Relationship to model containment because the hierarchy was not configured properly; the result is duplicated relationships and inconsistent rollups.

Field Service use cases

When a Service Appointment is dispatched to an Asset, the technician's mobile app can surface related Assets via Asset Relationship. Routes Optimisation considers related peers when computing whether a replacement triggers downstream testing. Maintenance Plans can be configured to fire on peer relationships in addition to hierarchical children.

Reporting and dashboards

Custom report types that join Asset to Asset Relationship and then back to Asset (twice) expose peer-to-peer reporting. Common dashboards include relationships per asset class, average peer count, and active relationship counts by Relationship Type. The double-join report type is the standard wrapper.

Sharing implications

Asset Relationship inherits sharing from the parent Asset records. Users who can see both endpoints see the relationship; users who can see only one endpoint do not. This is usually the right behaviour but produces surprising gaps when one Asset has tighter sharing than the other.

Common pitfalls

Three patterns recur. Using Asset Relationship for containment that belongs in Asset Hierarchy produces redundant data. Letting the Relationship Type picklist grow uncontrolled turns reports into noise. Forgetting to End Date relationships leaves stale peers that confuse field technicians and maintenance plans.

§ 03

How to set up Asset Relationship

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.

Gotchas

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.

Trust & references

Sources

Cross-checked against the following references.

Asset RelationshipsSalesforce Help
AssetRelationship API ReferenceSalesforce Developer Docs

Official documentation

Straight from the source - Salesforce's reference material on Asset Relationship.

Field Service OverviewSalesforce Help

Was this entry helpful?

Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

Test your knowledge

Q1. How does Asset Relationship differ from Asset Hierarchy?

Q2. What fields define an Asset Relationship record?

Q3. Why would you use Asset Relationships instead of parent-child hierarchy?

Discussion

Loading…

Loading discussion…

Back to Dictionary