Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies To: Project Operations Integrated with ERP, Project Operations Core.
The Project and Project Task entities now support time zone agnostic dates, enabling more flexible date handling across different time zones. To support this capability, the system adds new fields to both entities.
| Display Name | Field | Entity | Description |
|---|---|---|---|
| Start Date Time Zone Agnostic | msdyn_tzascheduledstart | Project | Start date of the project (Time Zone Agnostic) |
| Finish Date Time Zone Agnostic | msdyn_tzafinish | Project | Finish date of the project (Time Zone Agnostic) |
| Start Date Time Zone Agnostic | msdyn_tzascheduledstart | Project Task | Scheduled start time of the project task (Time Zone Agnostic) |
| Due Date Time Zone Agnostic | msdyn_tzascheduledend | Project Task | Scheduled end time of the project task (Time Zone Agnostic) |
Project entity
The new time zone agnostic dates on the Project entity are editable. When you edit a time zone dependent date, the system automatically calculates the corresponding time zone agnostic date, and vice versa.
Project Task entity
The new time zone agnostic dates on the Project Task entity are read-only. You must update the time zone dependent dates directly, and the system automatically calculates the time zone agnostic dates.
For existing projects, the system uses lazy loading to calculate time zone agnostic dates. The system populates them when you open the project main form for the first time. Until you open the form, these dates are empty in the database.
How time zone conversion works
The system automatically calculates time zone agnostic dates by using the project calendar's time zone as the reference.
With time zone agnostic fields (new)
The system displays dates based on the project calendar's time zone, so all users see consistent dates.
With time zone dependent fields (previous)
The system converts UTC to each user's individual time zone (set in personalization settings), so different users see different dates and times for the same project data.
Note
Automatic conversion to time zone agnostic dates uses the working hours from the project calendar. Ensure your project calendar has the correct working hours configured for accurate results.
Use time zone agnostic dates for reporting and display purposes only. The scheduling engine continues to use the time zone dependent dates for all scheduling calculations and operations.