Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Dynamics 365 Field Service - Preserve actual booking End Time when completion is recorded later

Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill Fernando

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, safely structured

We are announcing the ability to Preserve actual booking End Time when completion is recorded later in Dynamics 365 Field Service. This feature will reach public preview on November 22, 2026. How does this affect me? This feature allows Field Service administrators to choose whether completion by the booked resource automatically changes the booking End Time. Admins 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. 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. What action do I need to take? This message is for awareness, and no action is required.

What changed

Between the versions we saw, newest first
    • Title Dynamics 365 Field Service: Preserve actual booking End Time when completion is recorded later → Dynamics 365 Field Service - Preserve actual booking End Time when completion is recorded later
  1. · first version seen

These are the archive's capture times. They are separate from the versions returned by our reference tenants.

Read the archive's current copy

We are announcing the ability to Preserve actual booking End Time when completion is recorded later in Dynamics 365 Field Service. This feature will reach public preview on November 22, 2026. How does this affect me? This feature allows Field Service administrators to choose whether completion by the booked resource automatically changes the booking End Time. Admins 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. 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. What action do I need to take? This message is for awareness, and no action is required.

  1. Dynamics 365 Field Service - Preserve actual booking End Time when completion is recorded later Action date: Not supplied
  2. Dynamics 365 Field Service: Preserve actual booking End Time when completion is recorded later Action date: Not supplied

No related announcements were found in the saved public history. Check the source for newer announcements.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Some history or links were left out of the website export to keep it within its size limits.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current