#Salesforce Field Service47 personnes en discutent

Based on the Field Service Guide, our understanding is that if a Resource Absence is created without an address, it will calculate drive time for surrounding Service Appointments using the address on the Service Territory Member for the Service Resource. 

"If an absence doesn’t have an address, optimization uses the resource’s home base to calculate travel time to the next service appointment. For a more precise travel estimate, add an address to the absence, such as the location of the previous appointment or an address for the break."

We have been seeing examples where this is not the case. Below are screenshots showing the drive time for an Absence without an address versus the drive time when it's been updated with the Service Resource's home base.

Absence without an address:

Absence with the Service Resource's home address:

Updating the Absence with the address of the previous Service Appointment does not change drive time. Confirming that, without an address, the drive time for the Service Appointment following the Absence is being calculated using the address of the Service Appointment before the Absence.

Curious if there is something we are missing or if our understanding is incorrect.

Thanks!

Hi all,

I'm trying to use Maintenance Plans, specifically the "Generate on a floating schedule" functionality. My understanding is that this should allow the system to reschedule subsequent Work Orders based on the completion date of the previous one.

Here is my scenario and what I am trying to achieve:

• I set the frequency to every 30 days (on the Maintenance Work Rule, linked to the Maintenance Asset).
• The first Work Order (WO-1) is scheduled for November 15.
• The next Work Order (WO-2) is therefore initially planned for December 15.

My expectation (the "floating" logic):

• Scenario A: If I complete WO-1 early on November 10, the next Work Order (WO-2) should be automatically rescheduled for December 10 (30 days after the new completion date).
• Scenario B: If I complete WO-1 late on November 20, the next Work Order (WO-2) should be rescheduled for December 20.

The Problem: I have run several tests, but it seems that the SuggestedMaintenanceDate on the next Work Order never gets updated. It always stays at the original December 15 date, regardless of when I complete the first Work Order.

My Questions:

1. What configuration am I missing to make this floating schedule logic work correctly?
2. Which specific DateTime field on the completed Work Order does the system use to trigger this recalculation? Is it the EndDate on the Work Order object, or the ActualEndTime from the related Service Appointment?

Thanks so much for your help,  Salvatore

@* Salesforce Field Service * 

Hi all, in the Field Service mobile app (iOS), the Schedule tab appointment card shows the date month-first

("Tuesday, Aug 25, 2026") instead of UK day-first ("25 Aug 2026"). The times on the same card are fine (24-hour), so it's just the date ordering. 

Org Default Locale, the mobile user's Locale, and the device Region are all English (United Kingdom)

(ICU formats). There's no date-format option in Field Service Mobile Settings. 

Is this a known issue, and is there any supported way to control the date format on the card?

Thanks!