Twice a year, in April and October, we update the Compliance apps for Microsoft Dynamics 365 Business Central. This page gives the current release first, then the supported Business Central versions, then the changes per app. Older releases are in the archive.
7.2, October 2026: Advanced Permissions Management is released (first release). All apps support Business Central 29.
This is the one place where we state which Business Central versions we support. Other pages link here.
Policy for on-premises environments
- We release the Compliance apps for the five most recent Business Central versions.
- Release 7.2 goes back to Business Central 25. Release 7.1 went back to Business Central 24. Release 6.2 went back to Business Central 23.
- Before release 6.2, we released for all Business Central versions.
- Versions that are no longer in the range are not updated.
- Business Central online: you install the apps from Microsoft AppSource. See Getting started.
- Advanced Permissions Management is the exception. It needs Business Central 27 or later and is built for versions 27, 28 and 29.
Find the latest release for your Business Central version
| Business Central version |
Latest release |
Status |
| 14 |
5.2.202410NN.0 |
Last release. No longer updated. |
| 15 to 23 |
6.2.202510NN.0 |
Last release. No longer updated. |
| 24 |
7.1.202604NN.0 |
Last release for this version. |
| 25 and 26 |
7.2.202610NN.0 |
Current. Advanced Permissions Management is not available. |
| 27, 28 and 29 |
7.2.202610NN.0 |
Current. All apps, including Advanced Permissions Management. |
For on-premises environments, you can check the latest build for your version on our partner portal.
A version such as 7.2.20261028.0 has four parts:
7.2: the release, here 7.2.202610: the month, here October 2026.28: the Business Central version, here Business Central 28. This is the NN in 7.2.202610NN.0.0: the build number.
The NN is not a typo. It is replaced by the Business Central version for each build, so the same release has a different number per Business Central version. To see which release you have, look at the part before NN.
Advanced Permissions Management is released for the first time. We also fixed issues and added features in Field Security and Field Validation. Compliance Essentials, Advanced Permissions Recorder and Inventory Reconciliation get the same version number but have no functional changes.
- All apps support Microsoft Dynamics 365 Business Central 29 (2026 release wave 2).
- All apps have the version number 7.2.202610NN.0. See Read a version number.
- The list page for Action Security is now called Action Securities. See Securing actions.
First release. See Advanced Permissions Management for the whole app. The highlights:
- Records every change to permission sets, including changes made by app updates. See App updates and Change history.
- Lets you review the changes of a period as Reviewed or Flagged, with a comment, as evidence. See Reviewing changes.
- Shows who is affected before you change a set (what-if) and checks sets for risky patterns (quality check). See What-if analysis and Quality checks.
- Restores a user-defined permission set to an earlier version, and starts a clean tracking period with a baseline reset. See Rollback and Baseline reset.
- Builds a task-based baseline of permission sets from a curated library, with Copilot names and descriptions. See Permission set generator.
Field Security
Added
- A button shows the change log entries for the selected security. You find it on the Field Securities and Filter Securities overviews and on the Field Security and Filter Security pages. See Securing fields.
- When you finish the setup wizard, the new Field Security opens automatically.
Fixed
- Fixed: when you changed the permission sets on multiple lines with the option to remove the sets from all lines, the number of not linked permission sets did not change. Now it changes.
- Fixed: a Field Security existed and a new permission set with permission to modify the table was added. The set appeared in the Not assigned column, but the number did not change. Now the number changes when you run Calculate not linked Permission Sets on the Field Securities page. See the FAQ.
- Fixed: you could enter a Field No. that does not exist on a Field Security line. Now the field number is validated.
Filter Security
Added
- When you finish the wizard, the new Filter Security opens automatically. See Filtering records.
Fixed
- Fixed: permission sets were not calculated correctly when you added a security line. Now they are.
- Fixed: a Filter Security created with the wizard took its number from the Field Security number series. Now it uses its own series.
- Fixed: a message said that the line number cannot be zero or empty when you added a Filter Security line. Now you can add the line.
- Fixed: a Filter Security existed and a new permission set with permission to modify the table was added. The set appeared in the Not assigned column, but the number did not change. Now the number changes when you run the calculation on the Filter Securities page.
Added
- A checkbox runs the "bottom up check" on the related table when you choose No. of related records as the type. When it is selected, the app also validates the records of the related table, not only the records of the main table. See Table relations.
- Log entries for companies and permission sets also appear in the overview of change log entries. See Creating validations.
Fixed
- Fixed: the registration form did not appear when you registered from the registration warning. Now it appears.
- Fixed: a validation with a check on the number of related records fired wrongly when you deleted a record from the main table. Now it does not.
- Fixed: with the type Related Field, the table relation was removed when you chose the field. Now the relation stays.
- Fixed: after you changed the field of a table relation, the notification still showed the old field. Now it shows the new field.
- Fixed: the condition of a validation did not work when a table relation pointed to the same table. Now it works. See Table relations.
- Fixed: the cursor moved to the next line when you chose a field in a validation line. Now it stays.
- Fixed: the Sales Header example in the Copilot prompt gave an error when you tried to generate it. Now it generates.
No functional changes in this release (version update only). See Compliance Essentials.
No functional changes in this release (version update only). See Advanced Permissions Recorder.
No functional changes in this release (version update only). See Inventory Reconciliation.
Questions about a release? See Troubleshooting or email support@2-controlware.com.
Last reviewed: October 2026.