Version 1.3.0 – Coming Soon
Change Type | Description |
Enhancement | |
Enhancement |
Add new data validation types:
|
Enhancement |
Remove the ability to add fields that a data validation check is not valid for (For example FlowFilters and media fields) and obsoleted fields. |
Enhancement | |
Enhancement | |
Enhancement | |
Enhancement |
Add data validation action to documents that validates both header and line fields. An automatic check on document release can be enabled via setup. This is currently available on:
|
Enhancement |
Add 'Validate Data' action to the following additional pages:
|
Enhancement | |
Enhancement |
Add ability to automatically validate data on key master data when the blocked status is removed. |
Enhancement |
Add ability to use data validation templates as part of importing data using Configuration Packages. |
Version 1.2.1 – Release Date 24/02/23
Change Type | Description |
Enhancement |
Update App Logo - New Clever Branding |
Enhancement |
Business Central Compatibility Changes: - Update App to Runtime 9 - Tests: TestPermissions=Disabled - Fix Broken Product Hyperlinks in App.JSON |
Bug Fix |
Resolved Issue with Data Validation Templates Erroring on Validation |
Bug Fix |
Resolved Issue with Filter Expressions using Field Captions instead of Field Names |
Version 1.2.0 – Release Date 17/03/22
Change Type | Description |
Enhancement | BC20 Readiness - Extend Clever Apps Permission |
Enhancement | BC20 Readiness - Remove Permissions XML |
Version 1.1.5 – Release Date 19/10/21
Change Type | Description |
Bug | Convert Permissionset XML to Object |
Version 1.1.4 – Release Date 13/10/21
Change Type | Description |
Bug | Incorrect Flowfield Length for Field Caption |
Version 1.1.3
Change Type | Description |
Enhancement | South African English |
Version 1.1.2
Change Type | Description |
Enhancement | Support for default config |
Enhancement | Enforce licensing |
Enhancement | Update build definition to use template |
Version 1.1.1
Change Type | Description |
Enhancement |
Optionally Block Records That Fail Validation. Allow the user to determine if they want records that fail validation to be blocked e.g. if a item record fails validation then set the blocked flag to true. Add a new field to the Data Validation Template card, Block Records on Failing Validation. When the table ID is validated check if the selected table has a field called "Blocked". Only make the "Block Records on Failing Validation" field visible if there is a blocked field. If there is a blocked field, check that datatype of the field. If it is an option, show another field - "Blocked Value". This field should provide a lookup to the option string values (see FieldRef.OPTIONSTRING) so that the user can select the appropriate value i.e. for customer and vendors the user will need to decide whether to set the value to Ship, Invoice or All. If the user types directly into the field, validate that their entry is a valid option in the option string. When a record fails a validation rule and the template is set to Block Records on Failing Validation open a FieldRef to the blocked field: |
Enhancement |
If the field is a boolean, and blocked is not already true then set it to true and modify the record |
Enhancement |
If the field is an option, find the option value (integer) that corresponds to the Blocked Value from the template. If the Blocked field does not already have that value set it to that value and modify the record. |
Bug Fix |
Not checking Block Record on Failed Valid- COD9030389.BlockRecordOnFail check "Data Validation Template"."Block Record on Failed Valid.", exit if false. |