Get warned by AppSourceCop if your code validates against an obsolete version
This content is archived and is not being updated. For the latest documentation, go to What's new and planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
|Enabled for||Public preview||General availability|
|Admins, makers, marketers, or analysts, automatically||Jun 1, 2022||Jun 1, 2022|
When Microsoft obsoletes code, the obsolete tag is set to the version in which we expect the element or object to be obsolete. After an object has been marked as obsolete, another 12 months will pass before the object is actually removed. In some cases, this period might be longer.
A new AppSourceCop rule helps you validate early if your app is ready for a given release of Business Central without relying on Microsoft to actually remove the code. This way, you can plan more easily for and track against the compatibility of upcoming major releases—for example, as part of a continuous integration and continuous delivery (CI/CD) pipeline that validates on a regular schedule.
We've added a new AppSourceCop rule, AS0105.
With this rule, you can validate if your code is compliant for a given obsoleted version. You can control which obsolete version to test against by setting the new AppSourceCop property
Furthermore, the related BcContainerHelper commands
Run-AlPipeline support the new setting, and with AL-Go for GitHub, you can run a job that determines any upcoming obsoleted usage.
AppSourceCop Error AS0105 (docs)