Field Service ships Installed Product as a standard object once Field Service is enabled. The configuration work is page layouts and data import.
- Enable Field Service
Setup, Field Service Settings, enable. Confirm Installed Product is available in Object Manager after enablement.
- Configure page layout and FLS
Setup, Object Manager, Installed Product, set up the page layout, list views, and field-level security for the relevant profiles.
- Import existing equipment data
Use Data Loader to bulk-load Installed Products from the customer''s ERP or installation database. Match on serial number for upserts.
- Link to Service Territories and Accounts
Each Installed Product needs the Service Territory (where it physically lives) and the Account (which customer owns it). Populate these during import.
- Set up Maintenance Plans
Setup, Maintenance Plans, create plans linked to Installed Products. The plan defines the cadence; Salesforce generates Work Orders automatically.
- Build customer 360 reports
Build report types joining InstalledProduct to Account, Product, and WorkOrder. Surface them on customer-account dashboards for service and customer-success teams.
- Asset and Installed Product overlap in scope but are different objects. Picking one as the source of truth at project start avoids data duplication and confusion later.
- Parent-child hierarchies on Installed Product are not deeply nested by default. Multi-level hierarchies require custom configuration.
- Maintenance Plans only generate Work Orders for active Installed Products. Deactivating an Installed Product stops the maintenance schedule but leaves historical Work Orders intact.
- Installed Product is a Field Service-licensed object. Orgs without Field Service licenses cannot use it natively.