The long awaited Query Validation Tool (QVT) is now available as part of the H2 2021 Preview Release for Stories in People Analytics. This will build on the feature parity between our sustaining tools and our enhancements in Stories in People Analytics.
When you preview or finalise a query, it triggers some validation checks that help you identify and fix issues in the query, if any.
The validation checks return a list of missing or erroneous columns, calculations, and filters used in the query. Using the check results, you can update or delete the items in your query.
Details are in the What’s New Viewer here.
What is the purpose of the QVT?
The main purpose of the QVT will be to validate the queries being used on imported Story Reports from either the Content Store or from one of your different instances. This will ensure that the reports being run will be executed smoothly & customers can update the metadata mismatches between different instances.
The aim will be to replace the quick fix guides we had in place for the Content Store with a self-service tool within the Query Designer UI.
Pre-requisites to using the QVT?
- The customer must have People Analytics enabled in their tenant.
- The user must have the Create Story permission assigned to them in RBP.
How does the QVT work?
The QVT will run checks when a user is either previewing or finishing a query within the query designer UI. The checks will be done on both the columns (fields) & objects (tables).
- Columns (Fields):
The QVT will identify any fields used in the query which are not configured in the system. To resolve the issue, you can either replace the field or you can delete the field.
Note: The replace function will show all fields available from that table which are stored in the database. We would recommend choosing a field of the same datatype to ensure you don’t run into any other validation / configuration issues with your report.
The query will now preview successfully without validation errors.
- Objects (tables):
The QVT will identify any tables used in the query which are not present in the system. To resolve the issue, we need to remove the tables in question and any associated field with that table.