The Service Report section is a native system section and its position is controlled by the platform — it is not influenced by page layout ordering or app extension configuration.
In the Field Service mobile app the Create Service Report button appears:
This is Working As Designed (WAD). The Service Report button is a native system action in the Field Service mobile app and its position cannot be changed or reordered through any standard configuration today.
As a workaround you can try connfiguring a Field Service mobile flow and trigger it from an App Extension by following the below example steps.
-> Build the Field Service Mobile Flow
1. Go to Setup→ search"Flows"→ click Flow Builder
2. Click New Flow
3. Select Field Service Mobile Flow as the flow type
4. Click Create
Add Input Variables (to receive Work Order context)
5. In the flow, create an Input Variable:
Variable Name:recordId (or workOrderId)
Data Type: Text
Available for Input: Checked
This passes the Work Order Id from the mobile app into the flow
-> Add a "Create Records" Element to Generate the Service Report
6. Add aCreate Records element to the flow canvas
7. Configure it:
Label: e.g.,Create Service Report
Object:ServiceReport
Set field values:
a) ParentId - {!recordId} (the Work Order Id)
b) ServiceReportTemplateId - ID of your Service Report Template
8. Store the output record ID in a new variable (e.g., serviceReportId)
(Optional) Add a Screen Element for Confirmation
9. Add a Screen element after the Create Records step: Display a confirmation message like: "Service Report has been successfully created!"
-> Connect the Flow to the Field Service Mobile App via App Extension
Create Service Report (what technicians see)Note: Perform a fresh login to the Field Service mobile app and test the behavior.
005387444

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.