Modifier

Partager via

Microsoft Timeline for Deprecating Code in Business Central

  • Article

This article provides an overview of the timeline of when to expect code to be obsoleted once you start seeing warnings when extending it. To obsolete objects, the ObsoleteState Property and ObsoleteTag Property are used to specify where and when an object is marked as obsolete, for example, branch, build, or date of obsoleting the object. For methods and variables, the Obsolete Attribute is used for the same purpose. Some of the best practices for how Microsoft deprecates code can be seen in the Best Practices for Deprecation of Code in the Base App article.

When Microsoft obsoletes code, we intentionally set the obsolete tag to the version in which the element is obsoleted and not when the code will be removed. This is because our deprecation rules and timelines may change, and that releases and versioning schemes may change. Setting the version in which things are obsoleted is a statement of fact and doesn't change.

How long time from obsoleted to deprecated?

When an object is marked as obsolete, another 12 months will pass before the code is removed, in some cases even longer. Microsoft doesn't set a specific date for the removal due to engineering and architectural considerations. So, once you start getting warnings the feature or code won't be deprecated for at least two versions. If the tag is set to, for example, '18.0', the code will still be present in versions 19 and 20. We'll at the earliest remove the code in version 21.

When should I start refactoring?

When a major update of Business Central is released, and you start seeing deprecation warnings, it's encouraged to begin removing dependencies by refactoring the code. This work is important to do because once Microsoft does remove the code, the dependent app will be broken if it hasn't been refactored.

If you want to validate that your extension doesn't reference objects that are pending obsoletion with an obsolete tag version lower than a given version, you can use the AppSourceCop by setting the obsoleteTagMinAllowedMajorMinor in the AppSourceCop.json. For more information, see AS0105.

AL Development Environment
Directives in AL
Best Practices for Deprecation of Code in the Base App
ObsoleteTag Property
ObsoleteState Property
ObsoleteReason Property
Obsolete Attribute