The post Known Issue: View update button is not available for the upcoming service updates in LCS appeared first on Microsoft Dynamics 365 Blog.

The Microsoft Dynamics Lifecycle Services (LCS) team is happy to announce the immediate availability of the release notes for LCS (March 2019, release 2).

Configure your project for continuous service updates

With this release of LCS, you can now configure your project for continuous service updates from Microsoft. Customers and Partners can configure an update cadence for production environments, select an alternate sandbox to be patched prior to the production update, view the update calendar for the next six months, potentially pause getting updates to their environments, and get notified prior to an update all directly through LCS. Continuous service updates is a result of the feedback we’ve received from you over the last couple of months. For details about the features being released, refer to the announcement blog post and the One Version service updates overview documentation.

Self-service upgrade to version 10.0 and update 24 now available

Customers on versions 7.0 – 7.3 can now use self-service upgrade directly to application version 10.0 with platform update 24.  For information on self-service upgrade for your sandbox and production environments, please see the Process for moving to the latest update article.  If you’re running application version 8.0 you can use the simplified update process to 10.0.

Self-service upgrade critical hotfixes

With increased use of the self-service upgrade process, we have found several hotfixes to be critical to success for various target versions. For example, if you’re upgrading to version 7.3 a list of KBs that have consistently resolved issues with data upgrade, retail components, or performance will display.

The goal is to have this list empty before you start the Data Upgrade step of the process. These KBs need to be installed on your Upgrade-in-progress environment.

The post LCS March 2019 (release 2) release notes appeared first on Microsoft Dynamics 365 Blog.

We are happy to announce the availability of features that will enable you manage continuous service updates from Microsoft. Following are the different features we  are releasing today. Visit the One Version service updates topic for more details.

Configure Service Updates

This feature allows for the customer to be in control for when service updates will be auto-applied to the sandbox and production environment.  Customers also have the option to choose which sandbox environment for the auto-update to be applied.  This feature is currently available for customers on version 8.1.x and 10.0 to configure the Service Updates in Lifecycle Services.

Customers that are on 8.1.x version and higher will see a new notification in the project’s action center with a link to the Update settings page tab under Project settings where you can change the default update settings. 

NOTE:  This feature is currently only available to customers who are using Microsoft Dynamics 365 for Finance and Operations version 8.1 and later, and who are NOT part of the First Release program.  Microsoft is working to make the feature available to First release customers and customers who use older versions of the product.  For details on how to configure, see Configure Service Updates.

Pause Service Updates

Microsoft is committed to delivering cumulative service updates for our customers, although we know there may be circumstances when you will not be able to take the monthly service update.  We are pleased to announce the Pause capability in Lifecycle Services.  You can pause a maximum of two continuous updates at a time.  For details on how to configure see,  Pause Service Update.

Get notified about Service Updates

Microsoft uses service updates to update your configured sandbox and production environments to the latest version.  Several new notification types have been added with this release:

Email Notification

Notification bar on the environment details page

Upcoming updates schedule to reflect the updates that will be applied to that environment.

For details see, Get Notified About Service Updates.

Service Updates Schedule

After you set the update environment and update cadence, Microsoft generates an update calendar for the next six months to provide you with visibility and predictability of the Service Update.  This calendar shows exactly when the configured sandbox and production environments will be updated.  To view the calendar and learn more see, Configure Service updates.

The post Configuring LCS for Continuous Service Updates appeared first on Microsoft Dynamics 365 Blog.

The legacy user interface in the Business Process Modeler (BPM) is planned to be removed by the end of April 2019.

The new BPM user interface is the default BPM page, with feature parity to the legacy user interface. The legacy BPM interface will not be accessible from LCS after it’s removed.

Features that are in the legacy interface, but not in the new interface, will be enabled before the legacy interface is removed. These features include:

• Visio attachment indicator –  If there’s a Visio diagram attached to a business process, there will be a Visio icon added as a visual cue.
• Reviewed By and Reviewed At – After a process is marked as reviewed, the reviewer’s name will appear in Reviewed by field and the reviewed date/time appear in the Reviewed At field.
• Export to Microsoft Excel – Exporting processes from a BPM library will be supported from the new BPM user interface. 

These features above are planned to be released by in early March 2019.

The post Dynamics Lifecycle Services Legacy BPM user interface to be removed appeared first on Microsoft Dynamics 365 Blog.

Latest Update  – This issue has been resolved. We updated the impacted production environments with the critical update in the first week of March. We have not seen any issues since then.

Updated as of Feb 26th – We have determined the root cause and not all environments are affected by this failure. We are closely monitoring these failures in production and will update the environments that need this critical update this weekend. Sandbox environments have been updated and can be restarted if you see the issue.

On Monday February 18, 2019, some customers began experiencing failures for package deployment and other maintenance operations, such as database movement and upgrade triggered through Lifecycle Services (LCS) for their Dynamics 365 for Finance and Operations environments. We have been actively investigating this issue and have already made a fix that will address some of these failures. We are actively working to resolve the other failures. We will keep this post updated as soon as we have more information.

Symptoms – This may affect the maintain operations, such as apply updates, move database, upgrade, and maintenance mode. You may see increased times to complete and failures due to timeouts. This does not affect usage of the Finance and Operations client.

Mitigation – For sandbox environments, you can try using the Stop the environment and Start the environment options from the environment details page before starting any of the maintain operations noted above. If any operation fails, you can try to “resume” the failed operation from LCS. For production environments, please contact Microsoft Support.

We appreciate your patience as we work to resolve package deployments and other operations. For questions, please contact Microsoft Support.

The post Recent failures in servicing, database movement and upgrade appeared first on Microsoft Dynamics 365 Blog.

With our latest releases, partners with an Advanced Support for Partner (ASfP) support plan are now required to link the unique ASfP Contract ID/Access ID combination in LCS. For online incidents the default PartnerSource Business Center Account no longer applies.

If you do not know your unique Contract ID/Access ID combination, reach out to your account manager (TAM or SAM).  He or she can create one for you.

To link your Contract ID/Access ID to your account, complete the following steps:

From within a project, click Support from the main menu, and then click Manage Support plans.  Click Add contract.

Enter your Access ID and your Password or Contract ID, and then click Add contract.

The post Partner support plans in Lifecycle Services appeared first on Microsoft Dynamics 365 Blog.

The Microsoft Dynamics Lifecycle Services (LCS) team is happy to announce the immediate availability of the release notes for LCS (February 2019, release 2).

Implementation user role in project users screen

Now you can also specify the implementation role in the LCS while creating or editing the project users. There a new addition of toggle button to define if you allow Microsoft to contact. When this is enabled, Microsoft may contact the users based on the user role when appropriate. For example, Project managers will be contacted for Go-live assessments and architects will be contacted for any Architect workshops.

To update this, go to the Project users page and create/edit the existing user.

Restart services for environments deployed using self-service deployment

With this release of Lifecycle Services (LCS) we have added the ability for customers and partners to restart services directly through LCS on environments deployed using the self-service deployment option. This feature is available only on Sandbox (Tier 2 through Tier 5) environments and to users in the project owner or environment manager role. With this feature you will be able to restart AX, MR (Management reporter), or DIXF services. To use this feature, go to Maintain on the environment details page and select Restart service. This will open an option where you can select the service that you want to restart. The environment status will be updated to Restarting service and on completion will return to the Deployed state.

Access SQL database on environments deployed using self-service deployment

Today, on the sandbox environments (Tier 2 through Tier 5) deployed using the self-service deployment option, customers and partners have no way to connect to the Azure SQL database associated with this environment for troubleshooting or validation. Starting with this release you will now be able to request just-in-time access to the AX, MR (Management Reporter), and EDW (entity data warehouse) databases through LCS. On the environment details page you will see two new fields – Reason for access and Details as shown in the image below. After you select the reason to connect to the database, a request to create user specific credentials is submitted. The request is auto-approved and expires after 8 hours. Once approved the connection string and access details will be available on the environment details page. The access granted will be based on the reason that you select. For example, if the reason is AX troubleshooting then you will be granted read-only access to the database. If you select Performance tuning, you will be granted write access.

To connect to the Azure SQL database, you need to whitelist the IP address of the machine that will be used to launch SQL Management Studio. This can be done by adding a new Azure SQL firewall rule by going to the Maintain menu on the environment details page and selecting Enable access. Add the IP address of the machine that will be used to connect to the database and click Confirm. This rule also expires after 8 hours.

After the above step is complete, you can launch the SQL Management studio from the whitelisted machine and use the connection string and access details to connect to the required database.

Health metrics on environments deployed using self-service deployment

With this release of LCS, we have added a new tab to the environment monitoring page called Health Metrics, which shows critical metrics associated with environment, specifically the CPU consumption and Memory available. To access this, go to the environment details page, select the Environment monitoring link and click the Health Metrics tab.

The post LCS February 2019 (release 2 ) release notes appeared first on Microsoft Dynamics 365 Blog.

The Microsoft Dynamics Lifecycle Services (LCS) team is happy to announce the immediate availability of the release notes for LCS (February 2019, release 1).

Maintenance mode for environments deployed using self-service deployment

With this release of LCS, we’re adding the ability for customers to put their environment in maintenance mode for the environments that are deployed using the self-service deployment option. Maintenance mode is a configuration in Finance and Operations that allows system administrators to make system-wide configuration changes without much disruption. Once the system is in maintenance mode, only the system administrator can sign in and make the change. To use this feature, in LCS got to the Tier 2 and above Environment details page. Under Maintain, there is a new option called Enable maintenance mode. Select Enable maintenance mode to put your system in maintenance mode. After you are done making changes, the menu item under Maintain will have the option to Disable maintenance mode. Selecting this option will take the system out of maintenance mode. The environment history is updated on completion of this operation.

Database movement operations: Import and point-in-time restore

Database movement operations are a suite of self-service actions that can be used as part of Data Application Lifecycle Management (also referred to as DataALM). These actions provide structured processes for common implementation scenarios such as golden configuration promotion, debugging/diagnostics, destructive testing, and general refresh for training purposes.

In this release of LCS, the following operations are generally available for use on your Sandbox environments.

• Import database

To import a database prepared from a developer environment to a standard user acceptance test (UAT), or a database previously exported from a UAT environment, follow the steps outlined below:

• • 1. Go to your target sandbox Environment Details page, and select Maintain > Move database.
    2. Select the Import database option and choose your source database backup (.bacpac format) file from the Asset library.
    3. Note the warnings. Review the list of data elements that are cleaned up from the backup file.
    4. The import operation will begin immediately.
    5. After the import operation is completed, you must sign off on the operation before you can perform another servicing operation, such as package deployment, database movement, or upgrade.
• Database point-in-time restore (PITR)

To restore the database of a standard user acceptance test (UAT) environment to a previous point-in-time, follow the steps outlined below:

• • 1. Go to your target sandbox Environment Details page, and select Maintain > Move database.
    2. Select the Point-in-time restore option and choose a point-in-time.
    3. Note the warnings. Review the list of data elements that are not copied from the previous point-in-time.
    4. The restore operation will begin immediately.
    5. After the restore operation is completed, you must sign off on the operation before you can perform another servicing operation, such as package deployment, database movement, or upgrade.

Production point-in-time restore service request

For customers performing destructive testing in their Production environment as part of a ‘mock go live’ activity, the ability to roll back to a prior point in time has been made available via a service request.  To create this request, go to the Service Requests page from your Implementation project and find the Production Point-in-time restore type.

This is only for customers who are not yet live. If you are already live and need a point-in-time restore of your Production environment, it is advised to create a Support ticket.

Data upgrade preview package available for Dynamics365 for Finance and Operations version 10.0

Along with the previous announcement of version 10.0 (Preview), we have made data upgrade packages available in the Shared asset library.

These packages can be used on your DevTest environments to validate the data upgrade process from 7.x or AX 2012 respectively.  The ability to upgrade a Sandbox environment to 10.0 will become available when the 10.0 version is out of preview.

Validation for Financial Reporting Binaries on Database Refresh

One of the most common reasons for database refresh to fail has been that the binary versions of Financial Reporter are different between the source and target environments.  We now have added validation in LCS that will detect this scenario and prevent the refresh.

For instructions on how to correct the version incompatibility, please visit our documentation article:

https://docs.microsoft.com/en-us/en-us/dynamics-365/blog/unified-operations/dev-itpro/database/database-refresh#incompatible-version-of-financial-reporting-between-source-and-target-environments

The post LCS February 2019 (release 1 ) release notes appeared first on Microsoft Dynamics 365 Blog.

We’re excited to announce the release of Microsoft Dynamics 365 for Finance and Operations version 10.0 (April 2019) for preview through Lifecycle Services (LCS). This release is packed with some great features. To see what’s included in this release, check What’s New article. This is a Preview release and is not meant for Production use.

This release is available as an update package in the LCS Shared asset library, as shown below. You can import this package into your project and apply it on any Tier 1 or Tier 2 sandbox environments to preview the features. You will not be allowed to mark this package as a release candidate in LCS and apply it to a production environment.

The post Dynamics 365 for Finance and Operations version 10.0 (April 2019) is now available for preview appeared first on Microsoft Dynamics 365 Blog.

The Microsoft Dynamics Lifecycle Services (LCS) team is happy to announce the immediate availability of the release notes for LCS (January 2019, release 2).

Environment monitoring changes

Currently, because telemetry data is required to generate the Activity monitoring page, that data is queried when the page is loaded. (The query goes back 15 minutes from the current time.) In this release of LCS, the Activity monitoring page doesn’t load the telemetry data by default. Instead, the page is blank when it first appears, and customers receive the message that is highlighted in the following illustration. To see the data, they must enter a specific time and select Submit Time. All the data is then loaded on the page and is ready to use.

The post LCS January 2019 (release 2) release notes appeared first on Microsoft Dynamics 365 Blog.