
Announcements
What you’re seeing is expected behaviour in Dynamics 365 Field Service.
The Estimated Arrival Time (msdyn_estimatedarrivaltime) field on Bookable Resource Booking (BRB) cannot be cleared to blank because it is controlled by Field Service logic.
Not reliably.
Even if you clear it manually, via form edit, or via API/Patch, the platform will recalculate and repopulate the value.
Because Field Service uses this field as part of its scheduling engine, and several background processes enforce it:
If RSO or the built‑in scheduling engine is enabled, it automatically recalculates:
Estimated Arrival Time
Travel Time
Start/End times
Any blank value is treated as “missing required scheduling data” and is overwritten.
There are out‑of‑the‑box plugins on BRB that run on:
Create
Update
Status changes
These plugins enforce consistency between:
Start Time
End Time
Estimated Arrival Time
Travel Time
If one is blank, the plugin recalculates it.
If the BRB is tied to a Work Order, Field Service ensures the booking always has a valid ETA for SLA calculations.
Because ETA is a core scheduling field.
Field Service assumes that:
A booking must always have a valid arrival estimate
Removing ETA breaks travel calculations, route optimization, and SLA logic
So the system protects the field from being cleared.
If your goal is to “reset” the ETA, set it to:
The booking start time
A placeholder time
A recalculated value
This avoids plugin recalculation loops.
You can technically unregister the Field Service plugins, but this will break scheduling logic.
If you need a “user‑controlled ETA” that can be blank, create your own field and ignore the system ETA.
No, you cannot reliably blank out Estimated Arrival Time.
It is enforced by Field Service scheduling logic and plugins.
The system automatically restores the value because ETA is required for routing, travel time, and SLA calculations.
Use a custom field if you need a blankable value.