Lifecycle policy
The Dime.Scheduler extension for Microsoft Dynamics 365 Business Central supports every version of Business Central it has ever shipped for. What changes over time is not whether a version is supported but whether it is still being developed for, and that follows Microsoft's own Modern Lifecycle Policy for Business Central on-premises.
How the policy works
Microsoft ships a major version of Business Central twice a year, as a release wave in April and in October, and supports each one for 18 months from its release date. Dime.Scheduler tracks that window for development and keeps supporting what falls out of it:
- Supported means the connectorConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. keeps working on the version and problems you report on it are fixed. Every version in the table is supported, including the ones Microsoft itself no longer services.
- Active development means new Dime.Scheduler features are built and verified against the version. That is done for every version Microsoft currently supports, so a feature that ships this month is available on those versions and may not be on older ones.
The practical consequence is that an older version is a safe place to stay, but a quiet one: it receives fixes, not features. When a new capability matters to you, upgrading Business Central into Microsoft's supported range is how you get it. Since Dime.Scheduler is shipped as an extension, that upgrade needs nothing special on the Dime.Scheduler side beyond installing the matching extension version. See installation.
On-prem
The dates are the ones Microsoft publishes for its own support, in Pacific Time, and the active-development column follows them.
| Version | Released | Microsoft support ends | Supported | Active development |
|---|---|---|---|---|
| 2026 release wave 2, version 29.x | Oct 1, 2026 | Apr 6, 2028 | ✅ | ✅ |
| 2026 release wave 1, version 28.x | Apr 1, 2026 | Oct 13, 2027 | ✅ | ✅ |
| 2025 release wave 2, version 27.x | Oct 1, 2025 | Apr 6, 2027 | ✅ | ✅ |
| 2025 release wave 1, version 26.x | Apr 1, 2025 | Oct 14, 2026 | ✅ | ✅ |
| 2024 release wave 2, version 25.x | Oct 1, 2024 | Apr 5, 2026 | ✅ | ❌ |
| 2024 release wave 1, version 24.x | Apr 2, 2024 | Oct 8, 2025 | ✅ | ❌ |
| 2023 release wave 2, version 23.x | Oct 2, 2023 | Apr 3, 2025 | ✅ | ❌ |
| 2023 release wave 1, version 22.x | Apr 3, 2023 | Oct 9, 2024 | ✅ | ❌ |
| 2022 release wave 2, version 21.x | Oct 3, 2022 | Apr 15, 2024 | ✅ | ❌ |
| 2022 release wave 1, version 20.x | Apr 1, 2022 | Oct 11, 2023 | ✅ | ❌ |
| 2021 release wave 2, version 19.x | Oct 1, 2021 | Apr 13, 2023 | ✅ | ❌ |
| 2021 release wave 1, version 18.x | Apr 1, 2021 | Oct 12, 2022 | ✅ | ❌ |
| 2020 release wave 2, version 17.x | Oct 1, 2020 | Apr 13, 2022 | ✅ | ❌ |
| 2020 release wave 1, version 16.x | Apr 1, 2020 | Apr 13, 2022 | ✅ | ❌ |
| 2019 release wave 2, version 15.x | Oct 1, 2019 | Apr 14, 2021 | ✅ | ❌ |
| 2019 Spring release, version 14.x | Apr 1, 2019 | Oct 10, 2023 | ✅ | ❌ |
| 2018 October release, version 13.x | Nov 1, 2018 | See note below | ✅ | ❌ |
At any moment the active-development set is the three or four versions inside Microsoft's 18-month window: the two most recent release waves, the one before them, and for a few days after an April or October release, the one before that. A version leaves that set on Microsoft's end date, so plan an upgrade around those dates if you want to keep receiving new features.
Versions 13 and 14 predate the Modern Lifecycle Policy and were covered by Microsoft's Fixed Lifecycle Policy instead. Mainstream support for version 14 ended on October 10, 2023, and version 13 required an update to version 14 to stay supported by Microsoft at all. Dime.Scheduler still supports both. For Dynamics NAV, see the NAV lifecycle policy.
Cloud
Business Central online is updated by Microsoft on the same twice-yearly cadence, and every environment is kept within the supported range automatically. The Dime.Scheduler extension is published on AppSource and is validated against each release wave before it rolls out, so every cloud environment is on an actively developed version.