These are the archived release notes for 2024. The current notes are on Release notes. To read a version number such as 5.2.202410NN.0, see Read a version number.
With this release we fixed issues and added features to Compliance Essentials, Field Security, Field Validation, Inventory Reconciliation and Advanced Permissions Recorder. The version number is 5.2.202410NN.0.
- All apps support Microsoft Dynamics 365 Business Central 2024 release wave 2 (Business Central 25).
- During the installation wizard, the app asks whether to add the USE permission set to every user.
- New app: Advanced Permissions Recorder.
- Fixed: a table relation with the condition
<>'' gave an error message about the <>. Now it does not.
- Fixed: a blank space was not recognized as a character. Now it is.
- Fixed: the text in the Example column of the Calculated Filters overview was wrong. Now it is correct.
- Fixed: when you validated through a related record, a message said that a record was already opened. Now it does not.
- Copilot for regular expressions.
- Copilot helps you create a new regular expression.
- You can test values and use the new expression in a validation.
- It is available from Business Central W1 2024 and later. See Field Validation.
- The security message is easier to understand and mentions the correct values of the filter.
- Fixed: when you filtered Calculate Summary on Type = Permission Set and Source = SUPER, the summary did not show all users. Now it shows all users with that permission set.
- Fixed: an error occurred when the permission set SUPER (DATA) was part of the summary. Now it does not.
- Table relation after a table change.
- Before: you made a security line with a table relation and then chose another table ID in the header. The line kept the old table relation values.
- Now: the table relation values in the line follow the new table.
- Fixed: a Filter Security line with Filter Type = Editable, a table relation and a composite filter did not recognize the composite filter. Now it does.
- Several Field Securities for one table.
- Before: you removed a permission set from the assigned permission sets column of one Field Security. The set was also removed from the other Field Securities for that table.
- Before: copying sets to all lines copied them to the lines of all Field Securities for that table.
- Now: both actions affect only the lines of that Field Security.
- Not assigned permission sets.
- Before: the column No. of Not Assigned Permission Sets also counted system sets that you can only include in another permission set.
- Now: it counts only the sets that you can link to an account.
- Filters on the Contact List.
- Before: you created a contact with New from the Contact List, and the list had a filter on Type or Company No.. The filter did not apply to the new contact.
- Now: the filter applies to the new contact.
- When a Field Security has the default Not editable, you can add an error text only in the header.
Release 5.1.202404NN.4. This hotfix fixes three issues in Compliance Field Security.
- Fixed: the sign-in could be slow because of the new Expanded Permission setup of Business Central. Now the sign-in is optimized.
- Fixed: data ownership was not always calculated correctly. Now it is.
- Fixed: the summary and the unlinked permissions function did not always work correctly. Now they do.
With this release we fixed issues and added features to Compliance Essentials, Field Security, Field Validation and Inventory Reconciliation. The version number is 5.1.202404NN.0.
- All apps support Microsoft Dynamics 365 Business Central 2024 release wave 1 (Business Central 24).
- When you install the extensions, the app turns on the change log for the important setup tables automatically.
- In cloud sandboxes, Allow Http Clients must be on at app level. When it is not, Refresh License Information in the setup shows a reminder.
- Fixed: the button to remove recorded data when you record a session for a permission set did not work. Now it works.
¶ Field Security and Filter Security, 5.1
- Check your settings more easily.
- A Calculate Summary button on the Field Security page calculates the sources (users or permission sets) that belong to the secured table.
- On the Field Security Summary by Source page, you set filters on a source and run Calculate Summary again. You then see only the results for that filter.
- A second button calculates the unlinked users and permission sets of that security. The column Cause Permission Set ID shows why a user is not linked to the secured table.
- With this, you find an error in the setup and correct it easily.
- You can use characters such as open and close parentheses in the data of a related field.
- Allow precedes disallow.
- Example: a user has two permission sets that may change data. Set 1 is linked to security A, where only a few fields may change. Set 2 is linked to security B, where everything except one field may change.
- Now: the user may change everything except the one field that security B excludes.
- Fixed: loading the Default Data showed an error. Now it does not.
- You can use special characters such as parentheses and round brackets in the data of a related field.
- Renaming a Field Validation no longer loses its conditions, actions and comment lines.
- You can use a filter in a table relation.
- When several lines use a table relation, the validation warning shows all validations that need to be changed.
- Two validations of type Warning.
- Setup: Field Validation 1 (FV1) is on a table and has no actions. FV2 has an action that changes something in the table of FV1 through a table relation.
- Now: the trigger on FV1 does not start the action of FV2, unless the change is in the scope of FV1.
Last reviewed: October 2026.