2023.1 Release Notes
  • 28 Jul 2023
  • 4 Minutes to read
  • PDF

2023.1 Release Notes

  • PDF

Article Summary

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 2023.1 was released on July 17, 2023.

New Features

  • Snowflake as a data processing engine 
    • Leverage Snowflake-specific capabilities, such as amplified warehouse sizes, to process your data with lightning speed.
    • Compare test and control data directly in Snowflake so data doesn't ever leave your Snowflake environment.
    • To configure your data processing engines, simply navigate to the Settings menu and select Data Processing Engines.
    • Just like setting up storage in Snowflake, you can choose the processing engine that's best suited for each data source.
    • Learn more about the Powered by Snowflake architecture here.
  • Execute Python scripts directly in Validatar without having to install a data agent.
    • You can manage the available libraries under the Settings menu, specifically under the Scripting section.


  • Custom Field Improvements
    • You can now show or hide Custom Fields sections just like regular fields.
    • Custom Field Dropdown options can be archived for better organization.
    • Tag Custom Fields can now be managed more extensively.
    • The behavior of custom field archiving has been improved for a smoother experience.
  • Tasks will now cancel immediately when aborted from the activity page, including test execution, test materializations, profile set execution, job execution, and technical/custom metadata ingestion.
  • Job Schedule Improvements
    • You can limit the number of test results included in the job notification email.
    • You can choose to only send failed results in the job notification email.
    • New job steps use the currently active default settings to ensure the proper configuration is saved for the job step.
  • Scheduled lineage ingestions have been improved for a more seamless experience.
  • Technical and custom metadata ingestion errors are now displayed more clearly for easier troubleshooting.
  • Template tests script errors are shown in more detail when 'Preview Script' is clicked.
  • The UI/UX has been improved for better usability, and overall performance has been enhanced.
  • Improvements to API documentation and endpoints

Bug Fixes

  • Explorer
    • Duplicate profile records are no longer created when importing profiles into Snowflake, which caused loading problems in the Explorer.
    • The result trend now displays correctly in the Explorer when drilled down to the column level.
  • Data Sources
    • Data source connections can now be saved with passwords up to 300 characters.
    • Secret parameters are no longer cleared out accidentally while configuring Python-driven data source connections.
    • Global admins that are not already data source admins can now add new roles for a user on the Data Source permissions page.
    • Fixed a bug that caused a problem ingesting technical metadata if column names were longer than 200 characters.
    • Fixed an error that prevented Python-based connections from ingesting technical metadata correctly.
  • Custom Fields
    • Fixed a bug that unchecked child elements that were previously checked when exporting custom fields.
    • Custom fields shipped with Validatar no longer count toward the licensed custom field limit.
    • Fixed a bug that didn't allow new custom field configuration changes.
  • Testing
    • Template Test import files now import correctly, regardless of variable name case sensitivities.
    • Template Test result counts are now displayed correctly when the metadata is refreshed at execution time.
    • Unsaved variables in an open template test can now be referenced in the script builder.
    • The original script of a template is no longer executed after the child test is modified when executing the entire template test.
    • Fixed an error that sometimes occurred when creating a Validatar DQM Quick Start project.
    • Fixed a bug that incorrectly switched the result configuration settings in materialized standard tests.
    • Percent success criteria now show correctly when viewing test results saved to the repository.
    • Fixed performance issues with template test materialization that created a large number of folders.
    • The 'Matches' operator now appears on a standard test that's using regular expressions for a string dataset.
  • Jobs
    • The next run date of a job schedule is no longer overridden when the selected days of the week are modified.
    • Fixed a bug that was overriding Sunday job executions if the job schedule was resaved with multiple days of the week selected.
    • Fixed an error that didn't run the job's steps in parallel when a folder step was added to the job.
    • Fixed an error that prevented Tests (by Data Sources) from being added to the job steps as expected.
  • Lineage
    • Lineage metadata connection settings now correctly save parameter and data agent setting values.
  • Cloud Edition
    • Search results now display correctly when searching for items to add to a job in the Validatar Cloud environment.
  • PostgreSQL Environments
    • Resolved a bug where filters in Reports were case-sensitive.
    • Fixed an error that threw an error when using the search functionality while adding items to a job.
  • Overall Bug Fixes
    • Abandoned activities are now removed from the Activity page.
    • Breadcrumb inconsistencies and inaccuracies have been resolved.
    • Missing Result settings now apply correctly to profile tests.
    • Dates in exported reports are now displayed in the user's time zone instead of UTC.
    • Schedules can now be assigned to a time zone so that they accurately adjust with DST.
    • Fixed a bug that didn't rename a folder in the navigation tree when it was renamed in the folder list.
    • Fixed an error that allowed multiple Project and Data Source permission rows to be edited at the same time.

Was this article helpful?