Microsoft's Dynamics 365 Business Central is set to undergo a significant transformation with the 2025 Release Wave 1 (version 26). This update introduces an aggressive clean-up initiative aimed at removing unused and obsolete schema elements, including tables, table extensions, and table fields that have been in the Obsolete::Removed state for more than one major release. This strategic move is designed to enhance system performance, unify the codebase, and simplify maintenance processes.

Background and Context

Over the years, Business Central has accumulated numerous schema elements marked as obsolete but not yet deleted. These elements, while no longer in active use, continue to occupy space and resources within the system. By permanently removing these obsolete components, Microsoft aims to streamline the application, reduce technical debt, and improve overall efficiency.

Key Objectives of the Clean-Up Initiative

  1. Performance Enhancement: Eliminating over 10% of legacy tables and structures is expected to significantly boost system speed and reliability.
  2. Unified Codebase: The clean-up will lead to a consistent codebase across various regions, including Sweden, Denmark, Czechia, and India, facilitating smoother support and updates.
  3. Simplified Maintenance: A cleaner codebase reduces complexity, making it easier for developers to manage and apply future updates.

Technical Details and Implementation

The clean-up process will be automated, with the system set to drop any schema elements in the Obsolete::Removed state for more than one major release. This aligns with Microsoft's ongoing optimization strategy and breaking changes process. Developers are encouraged to refactor their code to remove dependencies on these soon-to-be-deleted objects to ensure compatibility with future releases.

Implications and Impact

  • For Developers: It's crucial to identify and update any code that references obsolete schema elements. Utilizing the CLEANSCHEMA preprocessor symbol can help anticipate removal timelines and facilitate proactive code adjustments.
  • For Partners: Partners should prepare for the clean-up by reviewing their applications for dependencies on deprecated objects and making necessary code modifications. Microsoft has provided resources and guidance to assist in this transition.
  • For End Users: While the clean-up aims to improve system performance and reliability, users may experience temporary disruptions during the transition period. It's advisable to stay informed about the update schedule and plan accordingly.

Conclusion

Microsoft's 2025 Release Wave 1 clean-up initiative represents a significant step towards optimizing Dynamics 365 Business Central. By removing obsolete schema elements, Microsoft is not only enhancing system performance but also ensuring a more streamlined and efficient platform for all users. Stakeholders are encouraged to review their systems and codebases to align with these changes and fully leverage the benefits of the upcoming release.

These resources provide further insights into the clean-up process and offer guidance for developers and partners to prepare for the upcoming changes.