skill-migrate

To handle breaking changes during a Business Central AL extension upgrade, migrate deprecated code and event signatures to maintain compatibility with the new BC release. Apply upgrade patterns across app.json updates and upgrade codeunits to ensure a smooth transition.

The safest way to plan a BC platform upgrade rollback is to use idempotent UpgradeTags and per-company validation. This approach ensures safe, repeatable migrations and minimizes production impact through pre/post-migration checks and risk assessment.

To update app.json for a BC version migration, align platform and runtime targets to the new BC version. Ensure dependency alignment and configure feature flags to properly target the BC release and prepare the AL extension for migration.

You need upgrade codeunits for AL extension data migration when moving extensions across BC platform versions. They handle data migrations and per-company validation, ensuring safe, repeatable upgrades and rollback-ready migrations during the transition.

Yes, this approach supports per-company validation for AL extension migrations. It uses idempotent UpgradeTags to ensure safe, rollback-ready migrations across BC platform versions while addressing breaking changes and deprecations effectively.

AL event signatures need migration during a BC upgrade to maintain compatibility with new BC releases. Addressing deprecated code and migrating event signatures are essential upgrade patterns to resolve breaking changes and ensure the extension functions correctly.