Dynamics 365 Project Operations: Optimize Project Operations - Use time-zone-agnostic fields in project planning
Summary
Project and project task start, and end times are saved in a date-time format. The system converts these times to GMT before saving them. When the product displays these times, it converts them back to the user's time zone. However, some integrations and customizations pull only the date from this field. This approach causes problems when the conversion to GMT changes the date. The problem happens when an integration pulls only that date from the field without converting it back to GMT.
To prevent this problem, create new fields on the entity to store the start and end date and time values without converting them to GMT. With these fields, you can confidently pull only the date without worrying about time-zone conversion causing the date to change.
Business Value
This feature helps you avoid time zone headaches when managing project schedules. Instead of converting times to GMT, which can shift dates and create confusion, it stores start and end dates exactly as you enter them. That means fewer errors, less rework, and more accurate timelines for your team.
Enabled for
Enabled for end users automatically
- Status
- In development
- General availability target
- Dec 2026
- Preview target
- May 2025
- Products
- Dynamics 365 Project Operations
- Clouds
- Worldwide (Standard Multi-Tenant)
- Release phases
- General Availability, Preview
- Platforms
- Web
- Added to the roadmap
- 16 Oct 2026
- Last changed
- 16 Oct 2026 · today
More Dynamics 365 changes
All Dynamics 365 roadmap itemsWhat changed
First observed 16 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.