The Microsoft Dynamics Lifecycle Services (LCS) team is happy to announce the immediate availability of the release notes for LCS May 2019 (Release 1) release.
Microsoft Customer Support has updated the severity description for incident submission. This change is reflected in Lifecycle Services (LCS). Please reference the updated severity description when submitting new incidents via LCS.
We revised the error message when the Business process modeler (BPM) to Azure DevOps synchronization failed. You will now be able to see the name of the failed process, the work item type, and the error message, including possible causes and suggested actions to resolve the error.
Here are some common causes and suggested actions to help resolving the error:
Today, on completion of any maintenance operation (servicing, database movement, upgrade, and putting system in maintenance mode) you have the option to sign off or sign off with issues. This is the last step to indicate completion of the operation. Only after you indicate sign off, is your environment ready for the next operation. With this release of LCS, the following changes we will be made to streamline the sign off process:
We are enabling a new database movement operation under the category of Point-in-time restore. Prior to this release, point-in-time restore has been used only for Sandbox UAT environments to go back to a previous restore point. Based on customer feedback we have added the option to take a restore point of the Production environment and restore that into a Sandbox UAT environment.
This will help customers and partners triage Production data-related issues that were previously working as required at an earlier date.
To use the functionality, select Maintain > Move databases > Point-in-time restore Prod to Sandbox from your Sandbox UAT environment details page.
The post Lifecycle Services – May 2019 (Release 1) release notes appeared first on Microsoft Dynamics 365.