These are the archived release notes for 2025. The current notes are on Release notes. To read a version number such as 6.2.202510NN.0, see Read a version number.
With this release we fixed issues and added features to Compliance Essentials, Field Security, Field Validation, Advanced Permissions Recorder and Inventory Reconciliation.
This release is not available for Business Central 14. The last update for that version is release 5.2.202410. See supported Business Central versions.
- All apps support Microsoft Dynamics 365 Business Central 2025 release wave 2 (Business Central 27).
- The version number of the extensions is 6.2.202510NN.0.
Fixed
- Fixed: the summary of the Field Security per source did not show the correct data right after you changed the linked permission sets of users. Now it does.
- Fixed: Field Security did not work correctly after you changed the Editable checkbox of a Field Security line. Now it does.
Added
- Copilot can generate a Filter Security from a prompt. You can change the proposal and save it as a new Filter Security.
- A new switch in the setup, Skip on Indirect Approval Actions. When it is on, indirect approval actions skip the Field Security and Filter Security checks.
Fixed
- Fixed: the number in the column Not assigned Permission Sets was wrong, and the action Calculate No. of not assigned Permission sets calculated it wrongly. Now both are correct.
Added
- Reference fields for notifications.
- Now you set these from the menu in the Field Validation Setup.
- For each table, you choose the fields to show in the validation notification.
- Display results in message.
- Now you can set this option per Field Validation.
- Use it when the validation runs from a certain type of page. A generated error can block further processing there.
- The switch Insert Check is now visible by default.
- Link several permission sets to one Field Validation.
- Before: you chose the permission set on the page.
- Now: use the Permission Set button to link several sets. The Field Validation then applies to these sets.
- On upgrade, the app moves your configured permission sets to the new table automatically.
Fixed
- Fixed: choosing Back after the first screen of the Field Validation wizard showed the registration screen. Now it does not.
- Fixed: a calculated filter in the initial values used the code instead of the calculated value. Now it uses the value.
- Fixed: a Field Validation with validation lines and validation actions for the same fields caused a recursive invocation error. Now it works.
- Fixed: a Field Validation with a related table and a check on the number of records gave an error about the conversion of an option field. Now it works.
Release 6.1.202504NN.1 (7 April 2025).
- Fixed: with some combinations of Field Securities and Filter Securities for the same table, Field Security did not work as expected. Now it does.
With this release we fixed issues and added features to Compliance Essentials, Field Security, Field Validation, Advanced Permissions Recorder and Inventory Reconciliation.
This release is not available for Business Central 14. The last update for that version is release 5.2.202410. See supported Business Central versions.
- All apps support Microsoft Dynamics 365 Business Central 2025 release wave 1 (Business Central 26).
- The version number of the extensions is 6.1.202504NN.0.
- Fixed: the date format was not recognized correctly. Now it is.
- The sign-in procedure is optimized for the case that there is no setup.
- The app now checks the date fields in Field Security, Filter Security and Field Validation. They must be logically configured.
- The Setup window of every Compliance app shows the Last License Check Error under License Information.
- HttpClient Request.
- In Compliance Essentials, this is the only toggle that must be On.
- When it is not, the license check of Field Security or Field Validation shows a message.
- The permissions in the Compliance permission sets are fine-tuned.
Added
- Filters in a Field Security.
- Now you can use additional filtering options.
- When the filter does not apply to a record, the Field Security is not valid for that record.
- So with Default Editable off, the user may change anything in a record that the filter does not match.
- Copilot can create a Field Security from a prompt. See the demo video.
- Select several fields at once.
- Before: you added the fields of a Field Security one by one.
- Now: you select all the fields you want to secure and add them as security lines in one step.
Fixed
- Linking a permission set is faster.
- The logic of the summary of Field Securities is improved.
- Fixed: the number of assigned permission sets was wrong. Now it is correct.
Fixed
- Fixed: the number of assigned permission sets was wrong. Now it is correct.
Fixed
- Fixed: not all available sessions were visible. Now all sessions are visible again.
Fixed
- Fixed: at sign-in, the app did not check whether a permission set linked in an Action Security applied to the user. Now it checks.
Added
- You can use calculated fields in the Init values fields.
- You can use a date formula and a calculated filter in a condition.
- A Copy button on the edit page copies a whole Field Validation, so you can start a new one from the original.
- A validation is also triggered when a change in the related table occurs.
Last reviewed: October 2026.