SelectZero 2026.3 is here, bringing a range of new features and improvements across the platform. This release focuses on deeper data quality insights, broader connectivity, and a more streamlined user experience. From row-level execution diffs and percentage-based test cases to AWS S3 integration and enhanced admin tooling, there is something for every team working to raise the bar on data quality.

Users can now see the differences between previous and new executions directly within the execution history. Each run is compared against the previous one, clearly showing which invalid rows are newly introduced, which have been resolved, and which remain active. This makes it easier than ever to track data quality progress over time and stay on top of recurring issues.

Note: Test case result CSV row limit has been reduced to a maximum of 10000 rows.

Users can now choose a new test case type that allows adding a separate SQL query for the total row count alongside the usual invalid row count query. When executed, SelectZero automatically calculates the percentage result, making it straightforward to define and evaluate proportion-based data quality rules without complex single-query workarounds. The invalid row count, total row count, and calculated percentage are all displayed in the execution results for full transparency.

It is now possible to see all upstream and downstream dependencies for any object, enabling simpler column-level impact analysis and root cause investigation. Derived from column-level lineage, this gives users a clear picture of what is affected when a data quality issue is discovered, as well as what upstream sources may be responsible for a failing test case.

SelectZero now supports connecting to AWS S3 via Amazon Athena, allowing users to query files stored in S3 buckets directly within the platform. This opens up data quality management for teams working with cloud-based file storage as part of their data infrastructure.

Links stored in custom fields are now rendered as clickable, taking users directly to the relevant external resource. This makes custom fields more useful for teams who reference external documentation, tickets, or tools as part of their workflow.

Admins can now view different log types directly within the platform without needing to download them first. The logs are accessible through the Logs modal, streamlining troubleshooting and reducing the steps needed to inspect platform activity.