In this blog, we look at several aspects of Dynamics 365 Business Central updates \u2013 what they are, the different types of standard updates and their general benefits, how the updates are released and the lifecycle for that purpose, and how to manage the updates \u2013\u00a0with particular emphasis on how awareness, planning and testing can streamline the release cycle to minimize business interruptions.<\/p>\n
The regular and occasional updates that Microsoft issues for Dynamics 365 Business Central make it a more productive, secure and efficient application in helping businesses plan agile and effective short- and long-term responses to their evolving operational challenges. We\u2019ll take an exhaustive look here at how the updates make that happen.<\/p>\n
This information can ensure the successful implementation of the updates by the people who are directly involved with that process \u2013 primarily Microsoft 365 administrators, D365BC consultants, and end users.<\/p>\n
There are many people with positions inside and outside of an organization who might play user roles in a Dynamics 365 environment<\/a>.<\/strong> These include multiple types of clients, as well as a variety of stakeholders within the business who could be concerned with how D365BC releases are configured in their areas.<\/p>\n Dynamics 365 Business Central updates can include functional enhancements \u2013 such as additional modules, improved reporting and new automation tools \u2013 that improve the core capabilities of the enterprise resource planning<\/a> (ERP) system; bug fixes, which are essential for maintaining the stability and reliability of the software; and performance improvements that can make the system run faster and more efficiently.<\/p>\n Other possible updates include:<\/p>\n As a growing number of businesses are applying D365BC internationally and managing multiple companies, Microsoft has expanded its capabilities to accommodate this trend in its past two update releases and intends to enhance the experiences of these participants in inventory, service and project management and establish more effective integrations with additional D365 applications.<\/p>\n All of this additional functionality that Microsoft is introducing to serve a growing universe of potential D365BC users makes it imperative that companies closely monitor any new developments from Microsoft.<\/strong><\/p>\n Hence, organizations using D365BC must stay informed about these updates and plan their implementation carefully<\/a> to ensure a smooth transition and take advantage of the latest features and security improvements. But it\u2019s also important to recognize that Dynamics 365 Business Central<\/a> is becoming an integral part of more types of businesses and to know why that\u2019s the case.<\/p>\n Dynamics 365 Business Central updates are released on a regular basis<\/a> \u2013 either monthly or as major releases \u2013 to provide users with new features, improvements, and bug fixes. The monthly updates usually come out on\u00a0 the first Friday of each month, while major releases, which introduce significant new features and functionality, usually happen twice a year, and align with the spring (i.e., April) and fall (i.e., October) release waves. (To review the full list of updates released in both waves in 2023, see the links at the end of this blog.)<\/p>\n Since the release lifecycle for either monthly or major releases is predictable, it gives businesses the opportunity to prepare for any upcoming changes.<\/strong> The standard process for releases usually consists of the following activities:<\/p>\n Microsoft offers a preview of these major releases for users and partners so they can access and test the new features before they are deployed to the general user base. This gives businesses an opportunity to provide feedback and ensure a smooth transition to the new version.<\/p>\n Microsoft publishes release notes for each update that outline the new features, improvements, and bug fixes included in the release. These notes typically are made available in advance to help users and partners understand the changes and prepare for updates.<\/p>\n Business Central is a cloud-based ERP solution, and Microsoft typically manages the underlying infrastructure and updates. This means that users on the cloud version get the updates automatically. However, Microsoft doesn\u2019t handle all aspects of the process. Administrators can control and manage the update implementation timing within their environment, as they are allowed to schedule the updates during off hours and test the release prior to publication.<\/p>\n Microsoft does this to ensure that updates are applied smoothly \u2013 which minimizes disruptions and user downtime.<\/strong><\/p>\n Administrators have more control over the on-premises deployments of D365BC updates. They can choose when to apply updates, taking into account factors like their organization’s schedule and compatibility with customizations. However, they\u2019ll need to follow Microsoft’s guidelines for updating the software.<\/p>\n When Microsoft releases these updates, you need to check the compatibility of any custom extensions or customizations. Some updates may require adjustments to extensions to ensure they work correctly with the new version. (To review the updated timeline for major and minor D365BC updates, see the link at the end of this blog.)<\/p>\n Knowing when to implement D365BC updates is just as important as knowing when Microsoft will release them and what they contain.<\/p>\n Effectively managing the scheduling of updates for Dynamics 365 Business Central is essential to ensure the smooth operation of your business processes<\/a> and keep your system current with the latest features and security patches. Here’s a general guideline on how to do this:<\/strong><\/p>\n You can keep yourself informed about the release schedule of D365 BC updates by checking the official Microsoft documentation or subscribing to their update notifications.<\/p>\n For cloud-based deployments, a notification email is sent to all notification recipients that are registered in the Business Central administration center. Check out our blog, The Dynamics 365 and Microsoft Power Platform Release Planner: 4 Benefits<\/a>, to see how this tool can help you manage Business Central releases.<\/p>\n Before scheduling an update, carefully review the release notes we mentioned earlier in this blog and assess whether the changes being introduced in the update align with your business needs and processes.<\/p>\n It’s best practice to have test environments (i.e., Sandbox or Development environments) that mirror your production environment. Test the update in these environments<\/a> to ensure that your customizations, extensions, and workflows are compatible with the new version. Users can make the test case list from their initial Business Central implementation a starting point to expedite testing and tracking of issues so that all business-critical functionality is tested.<\/p>\n Make sure you have a robust data backup strategy in place before you begin an update. Take a full backup of your Production environment to prevent data loss in case something goes wrong during the update.<\/p>\n Apply the update at a time when your business operations are minimally affected \u2013 usually on weekends or outside of regular business hours. For cloud-based deployments, your administrators can \u201cSet Update Date\u201d and \u201cSet Update Window\u201d within the DB365BC administration center to schedule times that are most appropriate for your business in each environment (I.e., Sandbox, Production).<\/strong> (The scheduled Sandbox environment update date should allow enough time for completing user testing and remediation of issues before you begin the scheduled update for the Production environment.)<\/p>\n Inform all relevant stakeholders \u2013 including users, administrators, and any external partners \u2013 about the timing of the scheduled update. Make sure they know that downtime may result. Be prepared for some downtime and try to keep it as short as possible.<\/p>\n During and after the update, monitor the system for any issues or unexpected behavior. This may involve checking logs, testing critical processes, and ensuring data integrity.<\/p>\n After the update, perform thorough testing to make sure that all your customizations, extensions, and integrations are working correctly in the updated environment.<\/p>\n In case the update creates problems that can\u2019t be resolved immediately, have a rollback plan in place. This plan should include steps to revert to the previous version of D365BC. For cloud-based deployments, Administrators can restore any environment (i.e., Sandbox and Production) to a certain point in time up to 30 days in the past.<\/p>\n If there are significant changes in the user interface or new features, provide training to your users so they can make the most of the updated system.<\/p>\n Keep detailed records of the update process, including what worked well and what didn’t. This documentation can be valuable for future updates.<\/p>\n Dynamics 365<\/a> Business Central is a powerful and versatile software tool for maximizing the functionality of your ERP system.<\/strong> Knowing all about its latest features through the release of D365BC updates and how to deploy them on a timely basis is the key to deriving optimal benefits from that tool.<\/p>\n For additional insights, check out these Microsoft documents.<\/p>\n Link to the major updates for 2023 wave 2 (i.e., October):<\/strong><\/p>\n Link to the Microsoft Learn Blog documentation on the updated roll-out timeline:<\/strong><\/p>\n \n What Is a Dynamics 365 Business Central Update?<\/h2>\n
\n
How Are Dynamics 365 Business Central Updates Released?<\/h2>\n
Early Access<\/h3>\n
Release Notes<\/h3>\n
Automatic Updates<\/h3>\n
On-Premises Updates<\/h3>\n
Extension Compatibility<\/h3>\n
How to Manage Dynamics 365 Business Central Updates<\/h2>\n
Stay Informed<\/h3>\n
Review Release Notes<\/h3>\n
Test Environments<\/h3>\n
Back Up Data<\/h3>\n
Choose the Right Time<\/h3>\n
Notify Users<\/h3>\n
Monitor the Update<\/h3>\n
Post-Update Testing<\/h3>\n
Rollback Plan<\/h3>\n
User Training<\/h3>\n
Documentation<\/h3>\n
Conclusion<\/h2>\n
\n
\n
\n