Northern Trail Outfitters wants to report on its Assets and reflect their attributes including hierarchical...

For this scenario, Salesforce Field Service should use custom Asset reports using Parent Asset and Root Asset. Parent Asset and Root Asset expose the hierarchical position of an installed component. Custom reporting can reference these fields to analyze Assets while preserving hierarchy context.

An Asset represents a customer-specific installed instance of a Product, which is why lifecycle, service history, hierarchy, installation dates, replacements, and component relationships should be modeled on Assets rather than on generic Product records. Work Orders can then reference the exact installed equipment being serviced.

The alternatives address different parts of the Field Service model. The interactive View Asset Hierarchy action is useful for navigation but is not the requested reporting solution, and standard Asset reports do not expose all hierarchy fields in the same way.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets — Asset hierarchy reporting; Parent Asset; Root Asset.