Release7.2.5.29
This release introduces bug fixes across Service Desk, Query Sheet, Lineage, Connectors, and Data Access, improving ticket security, download reliability, lineage accuracy, profiling results, and data loading visibility.
Key Highlights
Service Desk: Fixed unauthorized access to restricted ticket details by enforcing permission checks before displaying ticket information.
Query Sheet: Resolved an issue where sorted query results were missing from downloaded Excel files, ensuring all displayed records are included in downloads.
Lineage: Fixed Snowflake DBT lineage associations to link DBT models with the appropriate Snowflake tables and added missing S3 lineage for Azure Data Factory pipelines.
Connectors (Sybase ASE): Fixed missing row counts during profiling for tables and views, ensuring profiling results are reported accurately.
Data Access: Resolved the incorrect “No Data Exists” message in DAM while column data was loading, providing an accurate loading experience until the data is available.
Release Details:
Patch Release
Release7.2.5.29
release7.2.5.29.72529.de8b39f
September 15, 2026
Service Desk
Fixed
Resolved Unauthorized Access to Restricted Tickets
In Service Desk, an issue where ticket details could be accessed through a direct request even when access to the ticket was restricted has been resolved.
The access control has been corrected to verify permissions before displaying ticket details. Restricted tickets can no longer be accessed without the required permissions.
Query Sheet
Fixed
Resolved Missing Data in Sorted QuerySheet Downloads
In QuerySheet, an issue where downloading sorted query results as an Excel file generated a blank file containing only the column headers has been resolved. The issue occurred when the results were sorted by Program ID and Date. The sorted data was displayed correctly in QuerySheet, but the records were missing from the downloaded file.
The download process has been fixed to include all query results in the Excel file.
Lineage
Fixed
Fixed Snowflake DBT Lineage Association
In Lineage, an issue where Snowflake DBT lineage was incorrectly linked to the DBT model instead of the corresponding Snowflake table has been resolved.
The lineage mapping has been corrected to link the DBT model to the appropriate Snowflake table.
Resolved Missing S3 Lineage in ADF Pipelines
In Azure Data Factory, an issue where S3 objects used as sources or targets in ADF pipelines were not included in lineage has been resolved. As a result, lineage was not generated correctly for pipelines that used S3 objects as a source or target.
The lineage process has been updated to include S3 objects and generate the expected lineage for ADF pipelines.
Connectors
Fixed
Resolved Missing Row Counts in Sybase ASE Profiling
In Sybase ASE, an issue where the connector profiling job completed with partial success and failed to retrieve row counts for some tables and views due to insufficient permissions has been resolved. The profiling job processed all tables and views, but row counts were missing for some database objects.
The profiling process now handles these objects appropriately and reports profiling results accurately.
Data Access
Fixed
Resolved Incorrect “No Data Exists” Message in DAM
In Data Access Management (DAM), an issue where the Table Columns tab initially displayed “No Data Exists” while the column data was still loading has been resolved. The page could take 30–40 seconds to load the column data, causing the “No Data Exists” message to appear temporarily.
The loading behavior has been corrected so the tab displays the column data properly without showing an incorrect empty-state message.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?