How ‘One Version’ Affects Dynamics 365 Finance and Operations Users
In the past, a typical Dynamics AX upgrade from one version to the next could take months or years to deploy at a high cost – both financially and in labor hours. In 2018, Microsoft announced an “evergreen” ERP solution – Dynamics 365 Finance and Operations. This robust ERP business solution eases the burden and eliminates the financial stressors of an upgrade as all users are consistently on One Version.
Microsoft’s vision is that Dynamics 365 Finance and Operations One Version will help you stay current in a consistent, predictable, and seamless manner.
Previously, Microsoft planned on 10 updates each year. As of June 3, 2019, Microsoft announced changes to the update schedule that include only 8 updates each year. They also changed the minimum required updates for FinOps users to 2 per year from the original 4 per year.
When a new update is announced, users can log in to Lifecycle Services (LCS) and select the ‘sandbox’ environment that these monthly updates will be applied to and the weekend that they will be applied to production.
Once this is set up, you will get a notice two weeks before your production environment will be updated. This is when you should review the release notes and determine if any changes to your test plan are needed. The week before the production update your ‘sandbox’ environment will receive the update. You then should perform automated, end user, and integration testing. If there are no issues reported to Microsoft, your production environment will be updated at the time you specify. If there are issues, you submit a support ticket to prevent the production update. This will happen monthly unless you go into LCS and pause the process before your ‘sandbox’ receives the update.
Due to frequency of service updates to your system, it is more important than ever that you have a testing methodology and plan for your Dynamics 365 Finance and Operations implementation. A key to easing the burden of this monthly testing is the Regression Suite Automation tool (RSAT). Learn more about the RSAT tool in this article.
As you prepare for One Version here are some things you should be thinking through:
1) Who will be responsible for managing the updates getting applied to your Dynamics 365 Finance and Operations system? This individual should also work with your ISVs to determine if a new version of the ISV is required.
2) What will your schedule be for applying the updates? Will you take each monthly update or defer one (or two) months?
3) Will you have Microsoft automatically update your system or will you manually apply all patches?
4) Who will create and manage your test plan and execution? This should involve reading the monthly release notes to ensure your test plan covers any updates, ensuring that you get automated testing setup and that you have end-user testing as well as integration testing (if needed) for each release. This individual or team should also ensure that the testing did occur and sign off before the update can be applied to production.
Additional resources about One Version are below. Check out our webinar where we go over everything you should know about One Version and answer questions.
If you have any questions please contact us!
Regression Suite Automated Testing
- Create and Automate User Acceptance Tests
- Test Automation Suite for Dynamics 365 FinOps Part 1
- Test Automation Suite for Dynamics 365 FinOps Part 2