2022.2 Product Changes
  • 20 May 2022
  • 3 Minutes to read
  • PDF

2022.2 Product Changes

  • PDF

Validatar has a new release! From major updates to minor bug fixes, we're constantly working to improve your Validatar experience so you can continue to build trust in your data. Learn about what's new below.

Release Date

Validatar 2022.2 was released on May 6, 2022.

Get Started with More Options

  • Starting in 2022.2, you have the option to install Validatar using Linux and PostgreSQL.
  • Quickly learn how to best test and observe your data using our new step-by-step in-app guides.

Test Enhancements

Validatar is more than a source to target testing tool. We've highlighted our expansive testing capabilities by introducing the labels Test Data Set and Control Data Set to the testing interface. Learn more about this enhancement and other changes below.

  • We've given you more control over how Validatar should evaluate test results.
    • You can now decide how the engine handles missing values returned from the test.
    • We've expanded the result success criteria options to include exact matches, percent of test and control values, and custom calculations for more nuanced scenarios.
  • We've added a Jobs tab to the test details screen that lists all the jobs associated with the test.
  • Validatar immediately cancels tests when it detects syntax issues in the test or control data set SQL.
  • Use the new Child Tests tab inside of a Template Test to quickly navigate to the materialized child tests. Vice versa, we've added a link back to the Template Test to the child tests detail screen.
  • Perfect your SQL scripts directly in Validatar using the new Build Script feature, which prevents you from running the entire test to check for syntax or semantic errors.
  • Metadata isn't just logically linked to tests anymore. Navigate directly to the metadata object by clicking on the Metadata Link in the test.
  • We've replaced the View Runtime Configuration button with a Test Version tab on the test results screen.

Changed Test Result Warning
After upgrading, existing tests will have the Missing Key Settings configuration set to Fail by default. If you're expecting a record to pass even though the test or control value is missing from the result set, change the Missing Key Setting on the test.

Job and Schedule Enhancements

  • You can now run an entire test and job folder as a single job step. Just choose Folders(Run the entire folder) from the available job objects dropdown.
  • You'll now receive a warning if you attempt to delete a test that has a job currently referencing it.
  • We've added Sent to Top and Sent to Bottom buttons to the job steps list panel.
  • You can now add a name to job schedules. Any existing schedules will be named Schedule 1, Schedule 2, etc.
  • We've added the ability for you to copy jobs.
  • We've expanded template test configuration options to include not executing child tests inside a job.

Reporting Improvements

We've extensively broadened the types of reports you can create in Validatar by changing our Standard Reports to Standard Datasets.

  • The datasets are used to create custom reports needed to drive KPIs and trends.
  • Our new datasets are driven by secured views, which you can access in the Validatar database and use for external reporting. 
  • Dive deeper into details for tests, jobs, profile results, and metadata objects across all Validatar projects.
  • Don't worry. We still offer the Test and Job Execution and Event History reports.

Data Source Enhancements

  • We've added a Sample Profile to our standard profiles that return the top 50 column values as a sample set.

Other Enhancements

  • Automatically purge Event history with the new Event Purge Schedule.
  • When using Move/Copy in Tests, the folders in the tree are now closed by default to allow for easier navigation.

Bug Fixes

We've corrected bugs

  • Where the profile execution script was incorrectly linked to the profile execution in the user interface.
  • That prevented Custom Metadata exports from including the correct data source objects.
  • That prohibited the user from filtering string values correctly in Key-Value test results.
  • That prevents job schedules from running when SMTP settings are incorrect.
  • That prevents metadata from being ingested if a SQL Server database has multiple column-level extended properties.

Was this article helpful?