Work.com
Leading Through Change with Data
COVID-19 Data Hub
COVID-19 Global Daily Tracker
Global Economy Data Track
Government Data Track
Healthcare Data Track
B-Well Together
Leading Through Change
Salesforce Care
Leading Through Change Blog
Trailhead Resources
AppExchange Resources
MuleSoft Resources
< Back to List
Nick Sauer
FSL Service Report Template - Functionality Improvements
Customer Experience
FSL Service Report Templates have a number of limitations that make them very difficult to use. See other Ideas for Conditional Field Layout, HTML Section, Page Break and Text Wrap Ideas/Issues.Separately, the following should be addressed: Mobile App - Service Appointment for Work Order layout is the defaulted template, and this is not changeable by the User. This causes any mobile-created ServiceReport to be attached to the ServiceAppointment instead of the parent WorkOrderThere is no configuration to control this, and the api will not allow reparenting of the ServiceReport.As such, the current workaround is to: Clone the ServiceReportLink to parent WorkOrder (problem here is that the WorkOrder template version will override so this is not a like for like reparenting and thus usable in only limited scenarios).Delete old ServiceReportDelete old file against the ServiceAppointment Effectively, the only viable approach is to wait for File to be created from the ServiceReport, clone the File, reparent to the WorkOrder, and clean up the File/ServiceReport on the ServiceAppointment. There is no way to move the ServiceReport itself, so it becomes essentially useless. At the config level the ServiceReport available on mobile should be defineable so the customization is not required. As from the above, make the ServiceReport more customizable from the api, as opposed to an inaccessible intermediate object as it is today. Remove the 'Create and Send Report' button - allow configuration of this selection so it can be removed.Make the ServiceReport accessible in metadata so it can be migrated. Allow Clone of existing template.
Merge Idea · Flag
Arvind Batra - 3 months ago
Heiko Naumann - 1 year ago
Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.
Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.
Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.
Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.