What's New

Every six months we update our Compliance Apps with new features and bug fixes. On this page you have an overview of all updates based on our release notes.

All release notes are grouped below.

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. The problem is solved with this hotfix.

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 2022 (BC21) compatible;
The version number from the extensions is 3.2.202210NN.0 based on major.wave.YYMMbcversion.minor;
Adjustments were needed in BC21 for changes on default BC Permission functionality and tables in Business Central.

Field Security

It has been made possible to use the Filter Type ‘Visible’ on Allowed Companies for a user. An event on the page has been added for this;
Setting Filter Assign Permission Sets: With the option ‘Permission Sets with Access’ the system should show all the permission Sets with access to the secured table data or object 0. For Field Security the modify is needed, for Filter Security permissions sets with Insert, Modify or Delete permissions are shown. This did not work for all type of Permission Sets. The issue is solved;
When adding Permissions to a Field or Filter Security, the Permission Sets with the necessary permissions are shown. In the column NoOfLinkedUsers, the system indicates whether there are users with this Permission Set. This information was not always correct;
In the column No. of Not Assignee Perm. Sets the system does show the Permission Sets with permissions on the secured table data or object 0. In the column NoOfLinkedUsers, the system indicates whether there are users with this Permission Set. This information is correct now;
After registering the Field Security App, the system gave an error message. The error has been resolved;
In the Summary of Filter Security per Source also Calculated Filters are shown in field Filter 1 or Filter 2 when setup like this;
A Filter Security with more lines on the same filter gave a permission issue also when the linked Permission Sets are linked to the user. This problem is solved.

Field Validation

After registering the Field Validation App, the system gave an error message. The error has been resolved;
We add a new Validation Type ‘Calculated’ for Field Validations. This new Type validates on Calculated Filters. In the setup are some Demo Calculated Filters that you can use in the setup of your Field Validations. For example Date or User Filters.

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 2022 (BC20) compatible;
The version number from the extensions is 3.1.20220420.0 based on major.wave.YYMMbcversion.minor;
The code at login has been made a lot more efficient by using lists and dictionaries. Logging in to Business Central will be faster as a result;
To avoid problems with simultaneous login of different users, the license check has been optimized;
The migration of the permission sets linked to the Compliance extensions is now also made working in BC14.

Field Security

It is now possible to link comments to a Field and Filter Security;
Within the Summary of Field Security per Source, it has been made possible to navigate to the Field Security from the line, via Related, Field Security;
Calculate Summary Field Security per Source has been optimized making the calculation faster to complete;
It could happen that a filter value (option) was incorrectly stored in the filter security. Therefor the filter and the security did not work. This problem has been fixed;
When setting up a Filter Security on visibility it is not possible to use table relations. The system gives a message when selecting a table relation;
Within the Summary of Filter Security per Source, it has been made possible to navigate to the Filter Security from the line, via Related, Filter Security;
Calculating Summary Filter Security per Source has been optimized so that the calculation is completed faster.

Field Validation

Importing Field Validations gave errors in the configuration package. The issues have been resolved;
If field number 1 does not exist in a table, the system gave an error message when validating the field. The error has been resolved;
A Field Validation on a related field in combination with text fields can now only be set to Table Relation Validation Type 'Equal'. When selecting a different validation type, the system gives a message.

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:

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://docs.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://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 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 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 rights 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 rights;
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://docs.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://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 have made all of our apps compatible to the Microsoft Dynamics Business Central 2020 Wave 2 release, fixed some issues and added some feature to the extensions Compliance Essentials, Compliance Field Security and Compliance Field Validation. The new version is 1.2.0.20201027. Below you will find the most important issues and features.

Essentials

Load Default Data: from the page Table Relations you can now load default data. Click on the action Load Default Data to load our default Table Relations. Note: It is possible to load data several times.
Table Lock Isolated Storage: The interaction with the system table Isolated Storage could cause deadlocks. This is significantly improved.

Field Security

Multiselect Permission sets: When linking permission sets to a field, filter or action security, it is possible to select multiple permission sets so that they are linked to the correct security line in one action. In the permission sets screen, click on the dots, select more, and select the rows you want to link.
Licence Information: The licence information for the extension is improved. You can see the Status, Registration Date and when the Trial Expires. With a contract you can see the Contract Start Date and the Contract End Date.
Load Default Data: From the Field Security Setup and the Field Security Wizard, you can now load default data. Click on the action Load Default Data to load our default Table Relations and to load the Page and Action event subscriber information. Note: It is possible to load data several times. With the Action event subscribers, the linked Permission Sets will be overwritten so use this only a second time when needed.
Exclude Inactive Action Events: Inactive Action events (related to issue https://github.com/microsoft/AL/issues/942) are no longer subscribed to in our Action Subscriber Codeunit.
Filter on Field Security: A filter on the Field Security (header) did not always work. The problem is solved.
Field Show Permission Sets: The field Show Permission Sets in the Field Security Setup did not work as expected, this is solved.
Related Filter Security: The releated filter security did not work as expected, this is solved.

Field Validation

Regular Expression Validation: From now on Regular Expressions can be used as Field Validation. A Regular Expressions is a sequence of characters that define a search pattern for (in this case) input validation. From the Field Validation Setup you are able to load default data (Regular Expressions) that you can use in Field Validations, or you can setup your own validations in the page Regular Expressions. Select in the validation line the Validation Type Regular Expression, select the field to validate and select from the field Regular Expression the validation that you need.
Load Default Data: From the Field Validation Setup and the Field Validation Wizard, you can now load default data. Click on the action Load Default Data to load our default Table Relations and to load the demo Regular Expression codes. Note: It is possible to load data several times.
Permissions in 2C-FIELDVAL-USE: To use Field Validation you need the Permission Set 2C-FIELDVAL-USE. In this Permission Set we have added two permissions that were missing: Table 70196825 and 70196826.
Check Overview: The Field Validation Check Overview page did not expand and collapse as expected, this is solved.