Dynamics 365 Field Service: Preserve actual booking End Time when completion is recorded later Beta
Data as of 2 hours ago (26 October 2026)
Description
Business value Technicians do not always record booking completion at the moment work ends. They may update the booking later because of connectivity, customer-facing responsibilities, or end-of-day administration. When the later administrative action replaces the booking End Time, the recorded duration can extend beyond the work that was actually performed and affect downstream journals, time entries, labor costs, actuals, and work-order completion reporting. Field Service administrators can choose whether completion by the booked resource automatically changes the booking End Time. Organizations whose technicians complete bookings later can preserve the existing or explicitly supplied work end, helping booking duration and downstream time and cost records remain aligned with when the work occurred. Feature detail Use the organization-level Set End Time on booked resource completion setting in Field Service settings to control the automatic End Time update. With the setting set to Yes, which is the default, current behavior is preserved. When the booked resource completes a booking without supplying End Time, Field Service sets End Time to the completion time and recalculates Duration. With the setting set to No, Field Service preserves End Time and Duration when the booked resource completes the booking unless the completion request explicitly supplies a different End Time. Completion by another user or an integration continues to preserve End Time for either setting value. When the setting is No and the booked resource completes the booking, Field Service uses the retained or supplied End Time as the effective Completed booking timestamp. This keeps timestamp-derived booking journals and automatic time entries aligned with the recorded work end. Dataverse audit fields continue to show when the completion was submitted. The setting applies to future completion transitions and does not rewrite historical bookings. It does not change the booking-status lifecycle, invoice generation, or the existing Work Order Completed On calculation, which continues to use the latest eligible booking End Time.
Change history
Added to the roadmap 30 September 2026. Tracked here since 1 October 2026. Earliest target we recorded: February 2027 (since tracked — Microsoft may have moved it before we started watching).
Nothing has changed on this item since tracking began on 1 October 2026. Changes appear here as Microsoft updates the feed.