In Salesforce Field Service (SFS), Service Reports and Service Documents can be generated from multiple entry points, including Flows and deep links launched from a Lightning Web Component (LWC).
When an app extension with the API name Service_Report_Flow is created under Field Service Mobile Settings, Salesforce enforces a requirement that the associated Flow must run before a Service Report or Service Document can be created. When this extension is active:
The createServiceReport deep link is a URL-based trigger that allows a Lightning Web Component (LWC) to launch the Create Service Document action directly. It uses the following format: a URL beginning with the Salesforce Field Service protocol, followed by the record ID and the createservicereport action path.
When you attempt to launch Create Service Document from an LWC using the createServiceReport deep link while Service_Report_Flow is enabled, Salesforce displays the following error:
"Ask your Salesforce admin to use Service_Report_Flow for this link."
This error occurs because the deep link attempts to invoke the standard Create Service Report/Create Service Document action, which is unavailable when Service_Report_Flow is active.
The conflict occurs because the Service_Report_Flow app extension disables the standard service document creation path. The deep link relies on this standard path and cannot function while the extension is active.
To restore the standard behavior and allow the createServiceReport deep link to function:
Once removed, the standard Create Service Report and Create Service Document buttons are restored, and the deep link functions as expected.
If your organization requires the Service_Report_Flow to run before document creation, all service document creation must be routed through the configured Flow. Deep links that bypass this Flow are not supported when Service_Report_Flow is active.
The enforcement of Service_Report_Flow over the standard deep link path is intentional. Organizations must choose one approach: either use the Flow-based extension or use the standard deep link — not both simultaneously.
005306440

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.