Continuing toward our goal of having all customers on the latest version of Dynamics 365, today we are announcing the retirement of all legacy versions of Dynamics 365 for Project Service by the end of February, 2020. All customers must update to Project Service version 3.x by February 2020.

This change aims to provide all users access to the latest capabilities and improvements and offer a better support experience.

The following versions are impacted:

• Project Service versions 2.x and 1.x

We will continue to release regular updates on these versions until October 2019, and we will continue to provide support until December 2019.

Recent improvements are only available in Project Service version 3.x, so organizations using earlier versions are missing out on new capabilities, including:

• Improved scheduling experiences
• Configurable dimensions for resource pricing and costing
• Booking reconciliation views
• Modern WBS experiences
• Fluid and easy task assignment experiences
• Configurable and customizable time and expense entry
• Recalling or cancelling approval on an Approved time entry
• Multi-currency cost price lists and currency agnostic global price list for costs
• And much more.

Details on all these new features and more can be found on the Project Service documentation site.

You’ll find details explaining the new capabilities available with each major release in the release notes for Spring ’18, October ‘18, and April ‘19.

For steps to update, see Project Service upgrade considerations.

We’re excited for all our customers, who still are on the legacy versions of Project Service, to be able to take advantage of all the recent and future improvements as we continue to head toward new and exciting places.

The post Announcing end-of-life for Project Service legacy versions by February 2020 appeared first on Microsoft Dynamics 365 Blog.

Applies to: Project Service Automation for Dynamics 365 

We’re pleased to announce the latest update for the Project Service Automation application for Dynamics 365. This release includes some important improvements to quality, performance, and usability. 

This release is compatible with Dynamics 365 9.x. To update to this release, visit the Admin Center for Dynamics 365 online, solutions page to install the update. For details, refer How to Install, Update a Preferred Solution 

Project Service Automation (V 3.7.0.59)  

 Bug fixes 

• Fixed: Update Prices on Project Estimates creates an inaccurate calculation for project labor tracking remaining hours. 
• Fixed: Missing “Submit Request” and “Recall Request” buttons on Resource Requirement sub-grid. 
• Fixed: “A required field cannot be empty” error on the Name field appears when Quote and Contract line main forms are loaded. 

• Fixed: Correct error not thrown when project is in a state where changes are not permitted. 
• Fixed: Clicking “Open in MS Project” button from the Unified Client Interface (UCI) project should navigate to version 3.4+ . 
• Fixed: Performance issues during Project Task Assignment recalculations when upgrading from pre-assignment versions of the PSA(2.x) to PSA(3.6+). 
• Fixed: The Accounting date on Adjusted actuals should be set to the date of confirmation of the Correction Journal 
• Fixed: In Bulk Adjustment Journal it is possible to correct project without correcting task on the transaction. 
• Fixed: In Bulk Adjustment Journal – ‘Correct entries’ action does not handle Journal originating Actuals more gracefully. 

Project Service Automation Team  

The post Release Notes for Project Service Automation Update Release 7 appeared first on Microsoft Dynamics 365 Blog.

Applies to: Project Service Automation for Dynamics 365  

We’re pleased to announce the latest update for the Project Service Automation application for Dynamics 365. This release includes bug fixes. 

This release is compatible with Dynamics 365 9.x. To update to this release, visit the Admin Center for Dynamics 365 online, solutions page to install the update. For details, refer How to Install, Update a Preferred Solution 

 Project Service Automation (V2.4.12.11) 

Bug Fixes  

• Fixed: Update Prices on Project Estimates breaks Project Labor Tracking Remaining Hours. 
• Fixed: Potassium: Move bookings does not work as expected in some timezones. 
• Fixed: Missing “Submit Request” and “Recall Request” buttons on Resource Requirement sub-grid. 

• Fixed: Clicking Account Manager in new Quote\Contract throws unexpected error. 

Project Service Automation Team  

The post Release Notes for Project Service Automation Update Release 15, V2.4.12.11 appeared first on Microsoft Dynamics 365 Blog.

The Project Service (PS) solution will enable system-driven, automatic updates, in alignment with other Microsoft announcements that have highlighted the improved update process for Dynamics 365 (online):

• Modernizing the way we update Dynamics 365
• Dynamics 365 and Update Cadence – Business Applications Summit
• FAQ for Dynamics 365 Update Policies

New Project Service Update Policy:

• Manual updates lead to irregular and delayed updates which increase risks to the customer, support difficulties, and potentially increase downtime.
  • This required organizations to increase update planning and testing across their instances.
  • Leading to longer gaps between updates and often required deeper customer investments into their upgrade planning and testing.
• PS will move to an automatic update approach.
  • Many other solutions already push minor updates into customer orgs, automatically (i.e. Customer Service, Sales, and Marketing).
  • This will reduce customer risk, improve system supportability, and will make the update motion smoother and more predictable.

Project Service Version Eligibility:

• The new policy will be rolled out to instances with PS v2.4 and later as early as May 13th.
  • Microsoft will gradually exercise the new policy for instances eligible for automatic upgrade, so customers may not see any immediate impact to their eligible instances.
  • Customers can still update from the Admin Center if there is an update that has not yet been applied.
  • For instances with PS earlier than v2.4, customers should plan to manually upgrade the org to the latest available version, bringing them in line with the new policy.
• For customers using PS v3, the automatic update policy will be enabled in the months following enablement for PS v2.
• Stay tuned for upcoming information on the overall move from PS v2 to PS v3; however, Microsoft will not automatically upgrade any customers on PS v2 to PS v3.

Scope of the Automatic Updates:

• Project Service releases new updates of the solution roughly once a month with occasional hotfixes being released more frequently.
  • These monthly updates will include patches to resolve issues and may include minor functional, reliability, and performance improvements.
• For major updates, Project Service will follow the approach employed across Dynamics 365 for Customer Engagement.
  • Project Service will deliver two major updates per year, in April and October.
  • These will offer new capabilities and functionality.
  • Major new capabilities will be enabled in a public preview prior to this delivery period so customers can validate major updates in a sandbox environment.

Solution Upgrade Timing and Impact:

• PS updates will undergo testing to ensure the solution upgrades successfully while also safeguarding that no breaking changes are shipped through upgrade.
  • Major changes to the user interface, solution behavior, or significant new features will be shipped twice yearly after they’ve been available behind a preview.
  • Automatic updates will be completed during periods of low traffic for the hosting geographical region with minimal service disruption.

The post Automatic Update Policy for Project Service appeared first on Microsoft Dynamics 365 Blog.