Skip to main content
Featured group

* Salesforce Field Service *

Welcome! This group is dedicated to your success with Salesforce Field Service. Join the conversation here to stay up to date on the product, learn best practices, and everything in between. Use this group to review resources, ask questions, help each other, and share experiences. --------------------------------------- This group is maintained and moderated by Salesforce employees. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx

In Field Service, I'm using the work rule type “Field Service – Maximum Travel From Home.” 

 

  • When the Maximum Travel From Home Type is set to Distance with a value (e.g., 100), how is the distance calculated? Is it straight‑line (crow path) or street‑level routing?
  • If we switch the Maximum Travel From Home Type to Travel Time, we see three fields:
    • Maximum Travel From Home (minutes): How far (in minutes) a resource can travel from home to reach a service.
    • Travel From Home (minutes): How many minutes before the resource’s calendar start time can be used for travel. If empty, any amount of travel before the start of the workday is valid.
    • Travel To Home (minutes): How many minutes after the resource’s calendar end time can be used for travel. If empty, any amount of travel after the end of the workday is valid.

If I set Maximum Travel From Home to 120 minutes, does this mean appointments can be assigned within a 120‑minute travel range? Does it consider only one‑way travel time, or both outbound and return travel? And are the Travel From Home and Travel To Home fields essentially buffer times for the start and end of the day? 

 

Can both Distance and Travel Time constraints be used together in a single scheduling policy? 

 

and, in Field Service Settings > Scheduling > Routing, we have Enable Point‑to‑Point Predictive Routing enabled. The default travel speed is set to 10 MPH, which affects travel duration calculations and appointment assignments. Should predictive routing calculate travel speed dynamically (e.g., faster on highways, slower in city areas), or does it still rely on the static default value? 

 

Thanks, 

Yash 

 

@* Salesforce Field Service * 

2 answers
  1. Jun 13, 6:03 PM

    Hi @Yash Gosara

     Please see below: 

     

    1. Field Service – Maximum Travel From Home rule always uses aerial routing calculations regardless of whether point-to-point predictive routing or SLR has been enabled on the org. See product documentation here.

    .  

     

    2. When Maximum Travel From Home Type is set to Travel Time, the system calculates the distance using the Default Travel Speed defined under Field Service Settings -> Scheduling -> Routing (see product documentation here for more details).  

     

    This setting strictly considers one-way travel time/distance to reach the service appointment. In the example provided by you, the rule would ensure that a resource doesn't drive more than 120 minutes from their home base to get to their first appointment or any individual appointment, ensuring that they are routed within a 120 minutes travel radius from their home base. It does not aggregate the round-trip or return travel, or does not restrict travel time between individual appointments. 

     

    The other two settings (assuming you referred to these available under Field Service - Service Resource Availability rule) - Travel From Home (minutes) and Travel To Home (minutes) control how much travel time will be in resource's personal vs. company/scheduled time. For example, if the travel time to the first appointment is 60 mins, and Travel from Home (minutes) is set to 20 mins, the system will schedule 20 mins in resource's non-working hours, and 40 mins in resource's working hours. See more details in product documentation here

     

    The settings above are not buffers. If you want to add buffers (additional travel time for parking etc.) for each ServiceAppointment, you can configure travel time buffers at the org, service territory, or individual service appointment level to improve the precision of your scheduling operations. 

     

    For your question on using both Max Travel time constraint using distance and travel time in a single scheduling policy, could you explain the use case? If the need is to use different logic for different group of resources, you can leverage relevance groups to create more than 1 Max Travel from home base rule in the same scheduling policy. 

     

    Lastly, Point to point predictive routing does not use the static travel speed. It calculates travel speed dynamically using real road layouts, road types and historical time-of-day traffic patterns. You can setup Travel Modes per territory, resource, or both for accurate routing calculations based on transportation type, toll road preferences, and the presence of hazardous materials. The default travel mode is set to car, using toll roads, and not carrying hazardous materials. 

     

    Default Travel Speed under Field Service settings is used during aerial routing calculations only - when calculating Max Travel from Home base rule, or falling back to aerial routing when ESO cannot calculate predictive travel (for example - coordinates too far from an officially mapped road).

     

    Hope this helps!

0/9000

I have always found the Maintenance plans very clumsy to configure. There must be a simpler way to manage reoccuring maintenance jobs on assets on service contracts.  

 

Any good suggestions or is the best way to hide many of the settings and try to use flows to set them to default values?

1 answer
  1. Yesterday, 2:54 PM

    Hi @Joakim Franzen,

    I agree that Maintenance Plans can feel overly complex, especially for straightforward recurring maintenance scenarios. 

     

    I've found that a good approach is to keep the standard functionality but simplify the user experience by using Flows to prepopulate default values and automate as much of the configuration as possible. That way, users only interact with the fields that really matter, while the underlying complexity stays hidden. 

     

    It also helps to standardize maintenance templates for common service contract types, which reduces manual setup and improves consistency. 

     

    I'd be interested to hear if anyone has taken a more custom approach or found a lighter alternative while still leveraging the standard Field Service framework.

0/9000

Hi all,  

after recent updates the community user are unable to execute Field Service Mobile Flow using the "Complete" action of a Work Step. They receive an error that they are not allowed to run the flow now. 

I checked that all profiles has Run Flow permission, I tried to give direct access to specific flows to the profiles involved without results. 

 

All internal User are able to execute these flow using the "Manage Flow" permission... but the Community profile don't have this permission. 

 

How can I fix this? Is it a bug/issue or is now work as intended? 

Before recent updates community users were able to run these flows. 

 

Thanks

4 answers
  1. Yesterday, 8:49 AM

    Update for the errore message: It is "You can't run this flow. Ask your Salesforce admin for help."Update for the errore message: It is

     

     

0/9000

Hi, 

I would like to know if someone has already addressed this need. 

I have a client who wants the travel time to go from the first appointment not to be calculated, but for it to be calculated only from the end of the first appointment and the beginning of the second. The calculations between the other appointments being calculated normally 

Thanks

3 answers
  1. Heiko Lindner (Privat) Forum Ambassador
    Jun 11, 9:08 PM

    You can use the Work Rule Type: Service Resource Availability. There is the field called Travel From Home (minutes). Means the number of minutes that the resource has available for travel before the start of the work day (at the resource's expense). That's a fixed number than and not dynamically calculated.  

    An another option I can think about is, that the first appointment of the day does not have address available, means travel time will not be calculated. Add an resource absence a the valid address near by of the SA address and use this to calculate travel time to the next SA. Not nice, but a work around. With platform automation you could do it. I would prefer the fixed number via the work rule.

0/9000

Hello Trailblazers! 

 

We've got important news about the Salesforce Certification program. 

 

We want to share the following key updates to our roadmap:

  • 24 certifications will be retired. These include 15 Accredited Professional certifications and 9 Salesforce Certifications (across various roles & products).
  • 16 certifications will be renamed. This is happening to align with current Salesforce products and new branding, like the incorporation of Agentforce.

 

Retiring these exams helps us to:

  • Make your certifications more valuable: We align our certifications with the skills and expertise that hiring managers seek in the workplace.
  • Stay current with the product landscape: As Salesforce technologies evolve, our certifications are updated to reflect the skills professionals use daily.
  • Grow your skills where it matters most: We build certifications around the latest job roles, products, and features to give you the most relevant, in-demand certifications available today.

 

Key Dates

Mark your calendars (all dates are set to 12:00 a.m. UTC):

  • Friday, July 24, 2026: This is the last day to register for any retiring exams. And, this is the day all renamed certifications will officially go live.
  • Tuesday, August 31, 2026: This is the final day you can take any retiring exams.
  • February 1, 2027: The official retirement date for all impacted certifications.

 

What This Means For You

  • If you hold a retiring certification: It remains valid through the official retirement date of February 1, 2027, and you won't have any maintenance requirements in the meantime. These certifications will still be visible on your Trailblazer profile as part of your professional history.
  • If you are planning to pursue a retiring certification: You must register by July 24, 2026, and complete the exam by August 31, 2026.
  • If you hold a renamed certification: No action is required. The certification name on your Trailblazer profile will change on July 24, 2026. For information on how to request a new certificate with the updated name, visit Receive Your Salesforce Certificate and Logo After Earning a Certification

 

For the full list of impacted certifications, why we're making these changes, and what your next steps are, check out our official resources:

1 comment
0/9000

Missing Owner History Entry in Standard Salesforce Field History Tracking

 

I'm seeing what appears to be a gap in standard Salesforce Field History Tracking for the Owner field.

The history for a record shows:

Date/TimeFieldOld ValueNew Value

25-May-2026 03:03 PM | Owner | Default Admin | Mason Carter 

27-May-2026 01:29 PM | Owner | Customer Success Team | Olivia Bennett

The issue is that the last recorded owner change shows:

Customer Success Team → Olivia Bennett

However, there is no corresponding history entry showing how the owner became "Customer Success Team" in the first place.

Based on the available history records, the owner was previously recorded as:

Default Admin → Mason Carter

So the expected history would be something like:

Default Admin → Mason CarterMason Carter → Customer Success TeamCustomer Success Team → Olivia Bennett

But the intermediate transition:

Mason Carter → Customer Success Team

does not appear in Field History Tracking.

Questions

  1.  Can standard Salesforce Field History Tracking ever omit an Owner change? 
  2.  Are there scenarios involving Queues, Assignment Rules, Flows, Apex, or Scheduled Jobs where the owner can become a Queue without a corresponding history entry being created? 
  3.  Has anyone seen a similar situation where the Old Value shown in history references a state that is not represented elsewhere in the history records? 

This is standard Salesforce History Tracking (not a custom audit object). 

 

#Salesforce Field Service @* Salesforce Field Service *

1 answer
0/9000
3 answers
  1. Heiko Lindner (Privat) Forum Ambassador
    Jun 7, 2:15 PM

    It's not the only feature which isn't supported with the first release of the new scheduling console, unfortunately. 

0/9000

My global Optimization runs is not respecting one of the objectives in the scheduling policy. We have 2 types of service resources they can both do the same type of work we just prefer the system give the work to one over the other when ever possible. We control this using Skill level on the Service Resource Skills.  the Scheduling policy works and prioritizes these techs when using "get candidates" or "appointment booking" tools. but global optimization always gives it to the closest tech and seems to ignore the Skill level Objective even though there is a tech available with the with the higher skill level.    

 

In my Scheduling policy I have have an objective with a high weighting too prioritize BIR techs over FLM techs      

 

  1. Objectives and weightings. the Bir first the the objective looks for Most qualified skilled tech first this should prioritize one type of technicians before the other but it does not  Global Optimization ignoring Objective{A54B3111-C5E3-4493-83F7-B341001D6CFE}.png

has anyone faced this issue? 

 

@* Salesforce Field Service *

 

 

#Salesforce Field Service

4 answers
  1. Jun 6, 12:40 PM

    GO With Dynamic Scaling seems to prefer only Minimizing Travel and does not consider any other objectives

0/9000

Are there any limitations with Community Plus and Community Plus-login-based users managing field service inventory, i.e., creating and receiving Product Transfers from one location to the next

3 answers
0/9000

Hi everyone,    I'm observing unexpected behavior on the standard Location object regarding the RootLocationId field when reparenting a record across hierarchies. I'd like to confirm whether this is a known platform behavior or if I'm missing something.    Scenario:    I create a location inside another location,  Location A (ParentLocationId: null    RootLocationId: AAA)  --- Location B (ParentLocationId: AAA   RootLocationId: AAA)    If I change Location B to another Location, example:    Location C (ParentLocationId: null    RootLocationId: CCC)  --- Location B (ParentLocationId: CCC   RootLocationId: AAA (original))    My point is that RootLocationId remains unchanged all the ways.    What I already checked:  - ParentLocationId always updates correctly.  - The incorrect value of RootLocationId is confirmed directly via SOQL / 'Show All Data' (not a UI cache issue).  - LocationLevel is also not recalculated.  - The values persist over time, so it does not appear to be an async timing issue.  - According to the Field Service documentation, RootLocationId and LocationLevel are read-only fields calculated based on the hierarchy defined by ParentLocationId, so I would expect them to be recalculated when the parent changes.    My question:  Has anyone experienced the same? Is this a known behavior / known issue, or am I missing something? Has anyone successfully reparented a Location across hierarchies and seen RootLocationId and LocationLevel update correctly?    Any insight or workaround would be appreciated.    Thanks in advance!   

 

@* Salesforce Field Service * @* Salesforce Developers * 

1 answer
  1. Jun 4, 3:52 PM
    I don’t see it stated here, https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_location.htm, but root usually means “ultimate parent.” So a record with root set, and parent not set, I would say is somewhat illogical. Think sock is in drawer 1. Drawer 1 parent is bureau A. Bureau A’s parent is kid’s room. Kid’s room parent is my house. The location of red sock is drawer 1. The root is my house. Any blank parents I. Between “break” the hierarchy.
0/9000