Dynamics 365 Project Operations: Optimize Project Operations - Use time-zone-agnostic fields in project planning Beta
Data as of 1 hour ago (26 October 2026)
Description
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
Change history
Added to the roadmap 16 October 2026. Tracked here since 16 October 2026. Earliest target we recorded: December 2026 (since tracked — Microsoft may have moved it before we started watching).
Nothing has changed on this item since tracking began on 16 October 2026. Changes appear here as Microsoft updates the feed.