With this release we fixed some issues and added features to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation. Below you will find the most important issues and features.
General
- All apps are now Microsoft Dynamics 365 Business Central Wave 2 2023 (BC23) compatible;
- The version number from the extensions is 4.2.202310NN.0;
- A new Codeunit is available that can be used in a Job Queue. This Codeunit 70077733 ‘2C ES Create Users From AAD’ adds the users from Microsoft 365;
- Trying to use the Calculated Filters resulted in an error, this has now been solved.
- Recording of Permission Sets resulted in an error, this has now been solved.
Field Security
- We have added new functionality that makes it easy to Remove, Copy, or Replace the Permission Set(s) to all Security Lines. You can do this by selecting the Permission Set(s) and then clicking on one of the options in the menu on page Permission Sets per Field Security;
- It is now also possible to use the system table 2000000053 Access Control and 2000000006 Company in a Filter Security;
- In some cases the system gave an error message when removing a security line. This issue is solved;
- For a new security line, the system will now directly calculate the number of unassigned permission sets;
- You can add a custom error message In the Field or Filter Security. The system will use this message in the security errors. If ‘Default editable = true’ you are able to change the error for each field in the security. If not, the error message from the field in the header will be used;
- With the wizard you can setup a Field Security. After going a step back the system showed fields from another table. This issue is solved;
- The field ‘Show fields in summary’ in the Fields Security Setup is now by default set on ‘Only Fields in Field Security’;
- Operators in a Filter Security with a Table Relation did not work, for example the filter <>RAW MAT or RAW MAT| RESALE. This issue is solved;
- The number of calculated number of unassigned permission sets now shows the correct number;
- The page with a Filter Security now also shows a factbox;
- In a Filter Security it was not allowed to fill in a different error message in a line when this was already done in the header, this has now been solved;
- When copying permission sets to other lines, the option of Initial Field Entry Allowed is now also copied to the new permission set assignments;
Field Validation
- The page with Validation Results is more user friendly. The user can save his preferred columns;
- When more validations with different conditions for the same table are made, all validations will be triggered from now on;
- When changing the table-id in the header of a validation, a warning will now appear. When affirmative, all data in the validation will be reset, including conditions if these were already assigned;
- Using several conditions with table relations sometimes resulted in an error mentioning that a field cannot be found, this has been solved;
- When you removed a line and made a new one with a table relation, the screen to select a field for the conditions in that line was empty, this has been solved;
- When using UserID in a calculated Field Validation, this will no longer prevent the user from logging in.
Upgrade Instruction
You can upgrade to this version as follows:
- Cloud/AppSource: Follow the instructions as described on https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrade-appsource-app-in-prod;
- On Premises: Obtain the new version of the app from your partner or from us and follow the instructions as described on https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrading-extensions#running-the-upgrade-for-the-new-extension-version.
With this release we fixed some issues and added features to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation. Below you will find the most important issues and features.
General
- All apps are now Microsoft Dynamics 365 Business Central Wave 1 2023 (BC22) compatible;
- The version number from the extensions is 3.3.202304NN.0;
- With the installation of the Extension Compliance Essentials, the Azure Active Directory Application ‘Integration with Authorization Box’ will be created automatically.
The app has to be enabled manually after installation with the permissions SECURITY and SUPER (DATA).
Field Security
- On the Field Security card, we have added the Factbox ‘Permission Sets Assigned to Line’ so you are directly able to see which permissions are linked to the selected Field Security Line;
- Linking Permissions sets to a Field Security line is now possible via the column ‘No. of Not Assigned Perm. Sets’ by clicking on the number. In the page Link Permissions Sets you will see all the sets with Modify- permissions which are not linked yet. You can select the Permission Sets to link them with the button ‘Link Permission Sets’. After this the linked Permission Sets are visible by clicking on the number in the column ‘No. of Assigned Permission Sets’;
- Performance was not ok when a lot of Permissions Sets were linked to several Field Security Lines. We have solved this with a new Action that is available in the Field and Filter Security List and in the “Field Security Setup” page. With this action ‘Calculate No. of not assigned Permission Sets’ the number will be calculated. This means that the calculation is no longer performed continuously, which caused the performance issue;
- Calculation the Summary of Field or Filter Security per Source could give an error. This is solved;
- Permission Sets that are linked to Field Securities have an App-Id as a key field. When this App-Id is not correct, the security does not work. For this we created an action in the Field Security setup to Correct the scope and App-Id in the linked permissions sets if necessary;
- Field Security on system tables was not possible. We have modified this so that additional security can now be set up on the User- and User Personalization tables.
- After registering the Field Security extension, the License status was not updated correctly. This issue is solved;
- The system did a setup check whether the Permission Set 2C FIELDSEC USE is assigned to a user or not. The check has been removed;
- When a user has a Permission Set (with modify permissions to a table) that is not linked to a Filter Security for that table, this Filter Security should not apply to this user. However, this was the case. The problem is solved;
- The order of the columns on the Filter Security Lines page has been adjusted so that this makes more functional sense.
Field Validation
- It is now possible to set up a Field Validation for multiple companies. For this we have added a new table in which the relevant companies can be set. The existing field “Company” is automatically converted to a linked Company upon installation or upgrade;
- It is possible to check the table for a Field Validation. You will get the results in the Field Validations Check Overview. You can open related pages and correct the validation issues. After closing the page, you will see the results again and no longer the corrected record. This did not work properly;
- Field Validation Type length is now possible with min(0)..max(x) value. Value 0 allows leaving the field empty;
- The system did a setup check whether the Permission Set 2C FIELDVAL USE is assigned to a user or not. The check has been removed;
- In BC14 from to BC17 it was not possible to import the permission set 2C FIELDSEC USE due to an error in the XML structure. This is solved.
Upgrade Instruction
You can upgrade to this version as follows:
- Cloud/AppSource: Follow the instructions as described on https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrade-appsource-app-in-prod;
- On Premises: Obtain the new version of the app from your partner or from us and follow the instructions as described on https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrading-extensions#running-the-upgrade-for-the-new-extension-version.
With this hotfix we fixed an issue in Compliance Field Security:
- When a user has a permission set (with modify permissions to a table) that is not linked to a Filter Security for that table, this Filter Security should not apply to this user. However, this was the case. That problem is solved with this hotfix.