Skip to main content

#Salesforce Field Service61 debatiendo

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

3 respuestas
  1. 11 jun, 21:18

    Hi @Usman Khan

    thanks for the response. About your questione,  all community users are able to access to all object used in the Fiels Service mobile Flow. 

     

    Hi

    @Heiko Lindner, we haven't made any changes on our end. I believe the recent Salesforce update to Flow Access Restrictions is the cause of the problem. Running field Service mobile Flows from desktop isn't a common practice, and we've only recently noticed this issue affecting all external users and internal users who don't have the Manage Flow permission. I can't find the error directly right now, but it simply says "You don't have access to the Flow, contact your Salesforce administrator." I'll try to be more specific as soon as I can. 

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 respuestas
  1. Heiko Lindner (Privat) Forum Ambassador
    11 jun, 21:08

    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

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 respuesta
0/9000

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 * 

1 respuesta
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 respuestas
  1. 6 jun, 12:40

    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 respuestas
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 respuesta
  1. 4 jun, 15:52
    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

I've added a Status of "Confirmation Sent".  However the secondary category is still set to "Scheduled" - I believe this is necessary to have it still remain on the schedule calendar and dispatcher view.     The Gantt color is still showing as yellow[scheduled].   I've tried to switch from dynamic -> specific color of lavender but its not making a difference.  What would the correct way to show all Service Appointments marked as status "Confirmation Sent" in a unique color?    "Confirmation Sent" is the stage between scheduled and dispatched.   

 

See attached for new picklist value. 

 

Thank you!

FSL Gant Color - additional status

10 respuestas
  1. 4 jun, 2:25

    I've followed your advice @Benazir Beham and this has been working.   I've recently added another status - but when I try to assign it a color in the pallete I dont have this new option available to give it a color.    Almost like I'm missing a permission to this new status to assign it a color.   Would you be able to direct me?

0/9000

Hi, 

 

I have an LWC to create a record from the global action in FSL mobile app. This record is used to validate in the Change Status flow - if the record is available then the change status is allowed from Dispatched to In progress and if not, then we should an error message. The issue is even after the record is created when I try the change status flow, ending up with the same error message screen. Could this be sync issue? On the flow I am using the Get element to get the record to validate the condition. 

 

Please advise. 

3 respuestas
  1. Heiko Lindner (Privat) Forum Ambassador
    1 jun, 10:13

    Hm - pls. can you provide some more details. 

    • What record did you create?
    • What's your device using mobile SFS app, Android or iOS?
    • Are you in online or offline mode?
    • Whats the business process?

    Thanks

0/9000

I’m running into an issue where candidate actions tied to service appointments don’t appear for FSCs. When I log in as Admin, I can see them clearly in the Field Service Dispatcher Console. The user already has the Field Service Dispatcher Console permission set and license assigned, so this doesn’t look like expected behavior. Is there another configuration step or permission I need to enable to make these actions visible to FSCs?

1 respuesta
  1. 27 may, 20:02

    In the Field Service Dispatcher permission set, enabling the FSL.Gantt and List - Show Get Candidates custom permission allowed me to view the 'Get Candidates' action in the Dispatcher console.

0/9000