You create an Asset Hierarchy by setting the Parent Asset field on the records that should sit beneath a parent. There is no separate hierarchy object to enable. Build the parent first, then attach children to it.
- Create or open the parent Asset
Make sure the top-level installation exists as an Asset record, for example the full machine or system. This record becomes the root of the tree and usually carries account, product, and warranty details for the unit as a whole.
- Create the child Asset
Add an Asset for each serviceable component. Give it a clear name and link it to the same account and the relevant product so reports and work orders read cleanly later.
- Set the Parent Asset lookup
On the child record, populate the Parent Asset field with the parent you created in step one. Salesforce derives Root Asset and Asset Level automatically once the link is saved.
- Verify with View Asset Hierarchy
Open the parent record, use the View Asset Hierarchy action, and confirm the child appears nested underneath in the collapsible tree grid. The Child Assets related list on the parent should list it too.
A descriptive label for each record. Use names that identify the component, since the tree grid and related lists display this value.
The lookup on the child Asset that points to its parent. This single field is what creates the hierarchy.
The product the asset represents. Recommended on every record so hierarchy reports can group and filter by product.
- Root Asset and Asset Level are derived. Do not try to set them manually; they recalculate when you change Parent Asset.
- Granting a user access to the parent does not grant access to children. Configure sharing rules so service users can see the components.
- Keep practical depth to about four or five levels. Very deep trees slow SOQL that traverses Parent Asset and complicate reporting.
- Use Parent Asset for containment only. For replacement or upgrade links between peer assets, create an Asset Relationship instead.