Use derivations to map the fields on standard objects to fields required for
scheduling, including the Address and Service Territory (where), start and end times (when),
Scheduling Policy (how), and Work Type (what).
Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning
Experience
The Agentforce Field Service and Operations core features, managed package, and
mobile app are available in Enterprise, Unlimited, and Developer
Editions.
This is a Field Service managed package feature.
Choose any object and map fields from the record where the action is used so that the
values are automatically derived to the Work Order and Service Appointment created through
that action. Set default values from the object to the global action interface and override
the values.
Derivations apply to all field service scheduling actions of Appointment Booking, Get
Candidates, and Emergency Dispatch. Field mapping isn’t required, but mapping all fields
helps ensure that the appointment is scheduled properly.
From the App Launcher, find and open the Field Service
Admin app, and then click the Field Service Settings
tab.You can only map to the fields listed on the Field Service Settings tab.
Use
process automation to set additional fields.
Select Global Actions | Appointment Booking.
From the dropdown, select an object and click Add Object. After
you select the object, you can select fields from the source object to map to the service
appointment fields listed on the Field Service Settings tab.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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
Always Active
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
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
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.