Release7.2.4.6
This release introduces fixes across Query Sheet, Data Catalog, and User Management modules, improving data accuracy, query behavior, and user association visibility.
Key Highlights
Query Sheet Schema Mismatch:
Resolved schema validation to allow or restrict multi-schema queries based on system settings and crawled schemas.
Synapse Nullable Fields Display:
Resolved an issue where fields in specific tables were shown as NOT NULL despite containing NULL values.
Custom Views Temporary Objects:
Resolved an issue where temporary objects were visible in custom views created before migration.
User and Team Association Display:
Resolved an issue where users were shown as associated with teams due to legacy team data.
Release Details:
Hotfix Release
Release7.2.4.6
Release7.2.4.6.724684e7456
20th Jan 2026
Query Sheet
Fixed
Query Sheet Schema Mismatch
In the Query Sheet module, an issue occurred where a schema mismatch error was shown when queries used tables from different schemas, even when the system setting allowed multiple schemas. The issue has been resolved by applying the schema restriction rule correctly based on the system settings and crawled schemas. Now queries behave as expected when using one or multiple schemas.
Data Catalog
Fixed
Data Catalog Synapse Nullable Fields
In the Data Catalog module, an issue occurred where all fields in specific tables of Azure Synapse were shown as NOT NULL, even though many fields contained NULL values. The issue has been resolved, and now the Data Catalog correctly shows NULL and NOT NULL fields.
Data Catalog Custom Views Temporary Objects
In the Data Catalog module, an issue occurred where temporary objects were visible in custom views created before migration. The issue has been resolved by applying the correct filter after migration. Now, temporary objects are no longer shown in custom views, and the view behavior is consistent after migration.
User Management
Fixed
User and Team Association Display
In the User Management module, an issue occurred where users were shown as associated with teams due to legacy team data. The issue has been resolved, and now the Users tab shows accurate team associations.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?

