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.
Important
Dynamics 365 Project Service Automation has evolved into Dynamics 365 Project Operations. For more information, see Project Service Automation Transition.
The article highlights key upgrade considerations when moving to the latest release of Project Service Automation (PSA) version 3.x wave 1 2020.
Time entry
The time entry experience has been extended to deliver capabilities for extending time entry into more customer scenarios. This includes the capability to add entry types, which now drive specific behavior based on the field schema name Time Entry Settings, displayed as Time Source. A new solution, called Time, Expense, Statusing, and Approvals (TESA) has been added to support this functionality.
Upgrade consideration
To support this functionality, the roles within PSA have been updated to include new privileges. These privileges grant read access to the new entity, Time Entry Settings.
Users who require the ability to log time should be granted the user role Time Entry User in addition to existing roles. This role includes the new functionality and ensures that time entry will continue to work.
Additionally, if you have any custom app modules that include all forms for the time entry entity, you will be required to remove the TESA time Entry Quick Create Form from the module.
Currently extended time entry changes
To minimize the impact to current users of time entry, this role change is the only core requirement necessary to continue utilizing time entry. If you have created custom views or separate time entry experiences, you must set the Time Entry Setting fields to the correct PSA value.