With this release we fixed some issues and added features to the extensions Compliance Essentials, Field Security, Field Validation, Inventory Reconciliation and Advanced Permissions Recorder.
Below you will find the most important issues and features.
General :
- All apps are now Microsoft Dynamics 365 Business Central Wave 2 2024 (BC24) compatible;
- The version number from the extensions is 5.2.202410NN.0;
- During the installation wizard, the question will be asked if the USE permission set will have to be added to every user;
- We released a new app to record permission sets. The Advanced Permissions Recorder is a free app. You only have to register after installation before you can use it. This page in our wiki explains how this app can be used.
Field Validation :
- When using a table relation in a Field Validation and the condition <>’’ is used, this will not result in an error message regarding the <> anymore
- A blank space will now be recognized as a character
- The text in the Example column in the overview of the Calculated Filters is corrected.
- When validating using a related record to be validated, the error message no longer appears that a record is already opened
- To make it easier to create a new Regular Expression, we added a Copilot feature. You can test values and use your new created Regular Expression in Validation. This feature will be available only from Business Central W1 2024 and up.
Filter Security :
- The security message has been made easier to understand and now mentions the correct values regarding the filter.
- When using Calculate Summary and you filter on : Type = Permission Set and Source =SUPER, the summary will now show all users with that Permission Set.
- When calculating the summary, an error message will no longer occur when the permission set SUPER (DATA) is part of the summary.
- When a security line has been made with a table relation and afterwards another table Id is chosen in the header, the table relation values to be chosen in the line now follow the changed table data.
- A Filter security line with the combination of Filtertype = Editable, using a table relation and using a composite filter, now recognizes the composite filter correctly .
Field Security :
- If there are multiple Field Securities set up for the same table and you remove one permission set from the assigned permission set column in one Field Security. This set will no longer be removed from the other Field Securities too. This is also corrected when copying sets to all lines. The action will now only copy the set to the lines of that particular Field Security and not to the lines of all Field Securities made for that table .
- In the No. of Not Assigned Permission Sets column, only sets are now shown that you can actually link to an account. System sets that you can only include in an another Permission Set are no longer included here.
- When the user tries to create a new contact from “Contact List” via page action “New”, and the list has a filter applied on Type or “Company No.”, then for the new contact the set up filter(s) apply.
- When a Field Security is made with the Default set to “Not editable”, an error text can only be added in the header.
Upgrade Instruction
You can upgrade to this version as follows:
With this hotfix we fixed some issues in Compliance Field Security:
- The login process could be slow due to the new Expanded Permission setup of Business Central. With this hotfix, we optimized the login proces.
- Data ownership was not always correctly calculated. We fixed this in this hotfix release.
- The summary and unlinked permissions functionality was not always working correctly, this is resolved with this release.
With this release we fixed some issues and added features to the extensions Compliance Essentials, Field Security, Field Validation and Inventory Reconciliation.
Below you will find the most important issues and features.
General
- All apps are now Microsoft Dynamics 365 Business Central Wave 1 2024 (BC24) compatible;
- The version number from the extensions is 5.1.202404NN.0;
- When the extensions are installed, the change log on important setup tables for the apps are automatically enabled;
- In cloud sandboxes, “Allow Http Clients” on app level has to be activated. When this is not the case, the Refresh (check) License information in the setup will show a reminder to do so.
- When recording a session for a permission set, the button to remove the recorded data is fixed.
Field / Filter Security
- Functionality is added to make it easier to check Field- or Filter Security settings:
- A Calculate Summary button has been added to the Field Security page, which allows you to calculate the sources (Users or Permission Sets) associated with the secured table. On the Field Security Summary by Source page, you can set filters on a source and create a new calculation using the Calculate Summary function. When the calculation is complete, you will only see the results for the filter used.
- A second button is added to calculate the unlinked Users/Permission Sets concerning that particular security. In this summary you can see in the column Cause Permission Set ID why the user is not linked to the secured table. On this basis, you can find an error in the setup and correct this easily.
- Characters like open and close parenthesis can be used in the data of a related field;
- When a user has 2 permission sets which are allowed to change and one is linked to security A where only a few fields are allowed to change and the other is linked to security B where everything is allowed to be changed except for only 1 field, you are now allowed to change everything except for that 1 field mentioned in security B (allow precedes disallow);
- Loading of the Default Data doesn’t show an error anymore.
Field Validation
- Special characters like open and close parenthesis and round brackets can be used in the data of a related field;
- Renaming an existing Field Validation will not lose the Conditions, Actions and Comment Lines in that validation;
- A filter can be used in a table relation;
- When multiple lines use a table relation, the validation warning will now show all validations which need to be amended;
- In case of 2 validations (type Warning), FV1 on a table and without actions, FV2 with an action which changes something in the table of FV1 through a table relation, the trigger on FV1 will not result in the action of FV2, unless it is in scope of the validation of FV1.
Upgrade Instruction
You can upgrade to this version as follows: