How to Transition from Service Reports to Service Documents in Salesforce Field Service
In this Office Hours Insight session, Leigh-Anne Nugent walks through the practical shift from legacy service reports to service documents in Salesforce Field Service. The session covers what needs to be enabled, how templates behave across service appointments and work orders, and one important limitation teams should know before rolling this out in the field.
LESSONS YOU CAN TAKE FROM THIS:
1. Service documents need a few setup steps before they work smoothly
To get started, teams need to update page layouts, enable both Document Builder and Lightning SDK in Field Service Settings, and assign the right mobile document builder permissions to technicians. It is not a heavy setup, but it does require a few specific pieces to be in place before the mobile experience works properly.
2. Template behavior is not as flexible as it looks
A key insight from this walkthrough is that service appointment templates currently take priority in the mobile experience. Even when a work order template is defined, the system still appears to prefer the service appointment template by default. That creates friction for teams that want the work order version to drive the document experience automatically.
3. Images only follow the object where they are stored
Another important limitation is around photos. If you generate a service appointment document, it can only surface images related to the service appointment. If your photos live on the work order or work order line item, you need to generate the document at that object level to bring those images in. That makes document design and image storage strategy more important than it may seem at first.
4. The experience is cleaner, but still needs some tinkering
Once it is working, service documents offer a better field experience with template selection, signature capture, and generated files saved back to the record. But this session makes it clear that teams still need to test carefully, especially around syncing, cache resets, template defaults, and how related data is being pulled into the final document.
KEY TAKEAWAYS:
Service documents require page layout updates, settings changes, and permission assignment before rollout.
Service appointment templates currently appear to override work order templates by default.
Image galleries only pull photos from the same object as the template being generated.
Signature capture and generated file storage work well once setup is complete.
Teams should test template strategy, photo storage, and sync behavior before going live.
