Validation report
Summary: S Benson inquired about generating a comprehensive report from Collibra that lists all assets alongside their failed validations for easier distribution to data stewards. They expressed a need to streamline the process, highlighting the challenge of manually reviewing validations on a per-asset basis, especially when assets have multiple validation failures. S Benson is looking for a solution to avoid the time-consuming task of individually accessing and interpreting the validation results.
Several of my Asset Types have 20 or more validations. When I run a mass validation there are usually some assets that fail for multiple reasons. Has anyone been able to figure out how to get a report/spreadsheet out of Collibra that lists all of the assets and all of their failed validations?
I want to be able to send the report to my data stewards, rather than making them click on each failed asset and then read through the randomly organized validation results (one a time) so they can make changes.
Thanks,
Scott
George Cheung
·3 months agoOne of problem with validation rules and validation jobs is that they are done at the asset level and have to be triggered in order to recalculate the validation result. Another problem with the validation rules is that the asset model that the validation jobs can access is very limited to just the asset and its relations, nothing further.
The results of the validation job are also stored on the asset level - so if it failed any validation rule - the listing of which rule it failed would need to be retrieved on the asset level (navigating to the asset page and viewing validation result).
One alternative way of approaching validation is by using global views.
The global views would be searching for assets the fail the validation rule.
For example, a validation rule that verifies that an asset of a particular type must have the Description Attribute populated, the global view to create for this is one where the filter has the asset type specified, and the Description Attribute does not exist. The user can just navigate to this view to see which assets are missing Descriptions and take action from there.
The Global Views approach might not work for all cases.
Another alternative would be to use a daily workflow to get an email report of which assets fail certain validations throughout the system using the output module and programmable logic, see 'Daily Notification of Refresh Conflicts' for example of how the output module was used.