These are the archived release notes for 2021. The current notes are on Release notes.
With this hotfix we fixed an issue in Compliance Field Security:
After a new login of a user, only one Field Security was active, even if other Field Securities applied to the user. The error has been fixed.
With this release we fixed some issues and added features to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation. The new version is
2.2.20211019.0. Below you will find the most important issues and features.
General
All apps are now Microsoft Dynamics 365 Business Central Wave 2 2021 (BC19) compatible;
The version number from the extensions is 2.2.20211019.0 based on major.wave.YYMMbcversion.minor;
Until recently, Permission Sets for installed Extensions are stored in BC with Scope = 1 (Tenant). After upgrading the enclosed Permissions Sets from XML to Permission Set objects, these Permission Sets are stored with Scope = 0 (System). For BC18 and higher, we have a conversion function to change Access Control records for our own Permission Sets to set the Scope to 0 (System) as soon as we introduce the Permission Set objects. Also the already linked Permission Sets in the Compliance apps will be converted. The conversion can also be done manually from the Field Security Setup and the Field Validation Setup via Actions, Upgrade Tenant Permissions. This is only available if the conversion hasn't been done yet. In addition to the Scope adjustment, the compliance sets have also been renamed. The Minus Sign is no longer allowed and has been replaced by a Space;
Loading Default (Demo) Data will give a confirmation now. The Configuration Packages for this Data upload are renamed to make it more clear. When the Data is imported you can delete the Packages if wanted;
Using a Flow Field in a Table Relation has been made possible.
Field Security
Based on the setting Filter Assign Permission Sets in the Field Security Setup the system will now show the Permission Sets as follows:
Field Security: Number of Not Assigned Permission Sets: Show number and within lookup if modification permissions on the relevant table or table 0 = Yes. If the set has already been assigned, it does no longer count here and also no longer be shown with lookup. Number of Assigned Permission Sets shows the assigned Permission Sets and in the lookup the Permission Sets with modification permissions on the relevant table or table 0;
Filter Security: Number of Not Assigned Permission Sets: Show number and within lookup if Insert or Modify or Delete permissions on relevant table or table 0 = Yes. If the set has already been assigned, it does no longer count here and also no longer be shown with lookup. The lookup for the Number of Assigned Permission Sets shows the assigned permissions and in the lookup the Permission Sets with Insert, Modification or Delete Permissions on the relevant table or table 0;
In Filter Security, we made it possible to use calculated filters based on the logged in user. A Calculated Filter allows you to filter by System Variable (User ID, User Security ID and Current Company, by type Date Formula, for example -CW..CW for the current week, and by the logged in user where the system can use the table 91 (User Setup) and table 156 (Resource). In the User Setup the User ID is available. The filter on the Resource is based on the field Time Sheet Owner User ID. The Calculated Filters can be used in the Filter Security line. The field Filter Value Type must be set to Calculated. After that, a Calculated filter can be selected in the Calculated Filter Field. Examples of Calculated Filters can be imported from the Calculated Filters setup page with the button Load Demo Data.
Field Validation
The validation on Dimensions (Validate Default Dimensions) has been extended with a check on Dimension Combinations. Previously it was only checked whether the Dimension was filled and with what value, now it is also checked whether the Combination is allowed and if so with which combinations. When a Combination is limited or blocked you will get an error or a warning when you create or modify a Customer for example;
Field Validations are often based on Conditions. The Condition of a non-empty field did not work. We made this Condition (<>’’) possible again;
From a Field Validation, the entire table can be checked via the Check Table button. The Field Validations Check Overview is now improved. Some data was displayed incorrectly before;
It is now possible to add Comments on Table Relations and Field Validations.
Upgrade Instruction
You can upgrade to this version as follows:
1. Cloud/AppSource: Follow the instructions as described on https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrade-appsource-app-in-prod;
2. On Premises: Obtain the new version of the app from your partner or from us and follow the instructions as described on https://learn.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 some issues and added some feature to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation:
New pages instead of standard pages for web services: We have added some new pages that are used for views in the Authorization Box. Before, standard BC pages where used;
Table Relation on flowfiield for validation on Related No. of Records: it is now possible to use a flowfield in the setup of a Table Relation. This Table Relation can be used in a Field Validation or Filter Security;
Length Number Series: A No. Serie with more than 10 characters gave en error in Field Securities and Filter Securities. This problem is solved;
AB Batch Action Buffer: when using User Templates in the Authorization Box, an error could arise regarding to the Batch Action Buffer. This bug has been fixed.
With this hotfix we fixed the following issues:
The usage of IsolatedStorage by our apps could lead to locking problems. We have solved this problem;
In Field Validation, validating on empty values did not work as expected.
With this release we fixed some issues and added some feature to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation. The new version is 2.1.20210401.0. Below you will find the most important issues and features.
General
All apps are now Microsoft Dynamics 365 Business Central Wave 1 2021 (BC18) compatible;
The version number from the extensions are now conform Microsoft rules. The new version is v. 2.1.20210401.0 based on year.wave.date.version;
The webservices have been expanded for the connection with The Authorization Box;
Technical adjustments have been made in preparation for additional functionalities in the Authorization Box;
Translation issues are solved.
Field Security
The logic of our Field Security App is changed. In the old situation the security was valid for all users with the permission sets that were defined in the Field security line. The security could be overruled when the user has another not linked permission set with at least insert permissions of the same table where the Field Security was set for. In the new situation the user needs a not linked permission set with modify permissions to overrule the Field Security;
Also Filter Security is valid for all users with permission sets that are defined in the security. This is not the case if a user also has another not linked permission set with insert, or modify, or delete permissions;
Now Filter Security also works when you use the URL to go directly to a page with Filter Security;
New events are added for regular used pages so you can setup more visability security filters;
Summary of Field Security per Source and Summary of Filter Security per Source are optimized. With this functionality you can easily generate an overview including the users who are linked to the security settings. The Authorization Box also uses this information so that it can be shown within the analysis results for critical permissions;
There were some issues with loading default data. In the old situation it could be that when loading default data into the Field Security settings, the settings in the action security were removed. This issue is solved.
Field Validation
When validating default dimensions now the current value of dimensions is also shown in the error message for an better understanding of the error;
In a Field Validation you can use a related table in the conditions. Now the trigger is no longer executed by default when the field is updated in the related table. You can change the setting in the conditions by the checkbox Execute validation on Related Table modifications;
We have added the column Default Notification in het Regular Expression to make the validation messages more understandable for endusers.
Upgrade Instruction
You can upgrade to this version as follows:
1. Cloud/AppSource: Follow the instructions as described on https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrade-appsource-app-in-prod;
2. On Premises: Obtain the new version of the app from your partner or from us and follow the instructions as described on https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-upgrading-extensions#running-the-upgrade-for-the-new-extension-version.
Last reviewed: October 2026.