# Release7.2.5.9 This release delivers important fixes and enhancements across Data Catalog, Service Desk, Reference Data Management, Data Quality, Lineage, and Connectors. **Key Highlights** * **Data Catalog** * Fixed tag removal error to ensure proper tag management. * **Service Desk** * Fixed missing OAuth fields in ServiceNow integration. * **Reference Data Management** * Enhanced reference data view to support both column and table-level visibility, and extended access to Viewer license users through configuration. * **Data Quality** * Enabled viewing of Additional Associations in Published (Active) rules. * **Lineage** * Improved ADF lineage job stability and accuracy. * Fixed lineage status inconsistencies and rebuild issues. * Resolved SQL parsing, alias handling, and column lineage issues. * Fixed association mapping and duplicate association issues. * Improved configuration loading behavior. * **Connectors** * Fixed SQL Server crawl failure due to duplicate index entries. * Resolved IBM Cognos Analytics validation failure. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.9Release7.2.5.9.7259CAEACBD20th April 2026
## Data Catalog ### Fixed **Metadata Governance | Error while removing tag** In the Data Catalog module, while removing a tag from an object, an error message was displayed, and the tag was not removed. This prevented proper tag management. This issue has been resolved, and now tags can be removed successfully without errors. ## Service Desk ### Fixed **ServiceNow Integration | OAuth Fields Not Displayed** In ServiceNow Integration, while configuring ServiceNow integration with OAuth, required fields such as Client ID and Client Secret were not displayed, preventing proper configuration. This created an inconsistency with the documentation. This issue has been resolved, and now OAuth fields are displayed correctly and support proper configuration and validation. ## Reference Data Management ### New & Improved **Reference Data Management | Enhanced Reference Data View** In Reference Data Management, reference data was limited to column-level identification and did not provide a complete view of related attributes at the table level. Additionally, the module was available only for Author license users. This limited visibility and access for users. This enhancement enables reference data to be viewed at both column and table levels, enabling a unified view of related attributes and values. The module is also available for Viewer license users when enabled from Security > Applications. ## Data Quality ### Fixed **Data Quality Rule | Additional Associations in Published (Active) Status** In the Data Quality module, users were unable to view Additional Associations when the rule was in Published (Active) status and could only view them in Draft status. This limited visibility of associations for active rules. This issue has been resolved, and now Additional Associations are visible in both Draft and Published (Active) status, while adding objects remains restricted to Draft status. ## Lineage ### Fixed **Lineage | Azure Data Factory connector with the bridge** In the Lineage module, within the Azure Data Factory connector with the bridge, lineage jobs failed, and issues were observed in job logs during lineage processing. This impacted lineage visibility and reliability. This issue has been resolved, and now lineage jobs execute successfully with accurate lineage generation. **Lineage | Incorrect “Temp” status and rebuild inconsistencies** In the Lineage module, lineage was displayed as “Temp Lineage” even after a successful build, and rebuilding lineage sometimes resulted in a failed status despite available lineage. This created an inconsistency in lineage status. This issue has been resolved, and now lineage status is displayed accurately based on build results, ensuring consistency between job logs and UI. **Lineage | Amazon Quicksight lineage status inconsistencies** In the Lineage module, within the Amazon Quicksight connector, source tables were identified incorrectly, temporary tables were not handled properly, and lineage status was shown incorrectly. This affected the accuracy and visibility of lineage. This issue has been resolved, and now source tables are identified correctly, temporary tables are handled appropriately, and lineage status is displayed accurately. **Lineage | ADF pipelines old associations not deleted** In the Lineage module, during lineage rebuild for Azure Data Factory pipelines, older associations were not deleted, resulting in incorrect and duplicate associations. This impacted lineage accuracy. This issue has been resolved, and now existing associations are properly deleted during lineage rebuild before creating new associations. **Lineage | ADF SQL Alias Handling Issue** In the Lineage module, while building lineage for ADF pipelines using SQL as a source, column aliases were not picked correctly, and lineage was mapped to unrelated columns. Also, the query was displayed in a single line in the “Correct Query” screen. This issue has been resolved, and now column aliases are picked correctly, lineage is mapped to the correct columns, and the query is displayed in a proper format. **Lineage | Missing column lineage in Simple Lineage Pipelines (Salesforce source)** In the Lineage module, column lineage was missing in Simple Lineage Pipelines where the source is Salesforce, even though table lineage was built. This caused incomplete lineage tracking. This issue has been resolved, and now column lineage is correctly generated after rebuilding lineage, with fixes handling missing metadata scenarios. **Lineage | Column lineage issues in complex ADF pipelines** In the Lineage module, column lineage was not fully built for complex Azure Data Factory pipelines, with missing source columns and inconsistent job log messages for non-existent columns. This resulted in incomplete lineage visibility. This issue has been resolved, and now column lineage is built correctly with proper handling of source columns and accurate job log messages. **Lineage | ADF SQL Parsing Issue for Column-level Lineage** In the Lineage module, while building lineage for Azure Data Factory pipelines using SQL as a source, column-level lineage mismatching occurred due to incorrect SQL parsing. This resulted in incorrect column mapping. This issue has been resolved, and now SQL parsing correctly identifies source tables and columns, ensuring accurate column-level lineage. **Lineage | SSIS associations mapped with different connections** In the Lineage, after executing the SQL Server Integration Services (SSIS) lineage, associations were incorrectly mapped with objects from a different connection, leading to incorrect lineage relationships. This impacted data traceability. This issue has been resolved, and now associations are correctly mapped based on the appropriate connection. **Lineage | Advanced Job Release Properties Loading Issue** In the Lineage module, lineage and advanced job release properties from ovaledge.war were loaded instead of the properties files during runtime. This caused an incorrect configuration to be applied. This issue has been resolved, and now property files are used instead of the bundled configurations during runtime. ## Connectors ### Fixed **Connector | SQL Server crawl failure due to duplicate index entries** In Connector, during crawl operation for SQL Server connector, duplicate index entries caused errors and crawl failures. This impacted metadata ingestion. This issue has been resolved, and now index handling prevents duplicate entries, allowing successful crawl execution without errors. **Connector | Cognos Validation Failure** In the Connector module, IBM Cognos Analytics validation failed even though the connection details, such as credentials, endpoints, and configuration parameters, were correct and working from the source system. This issue occurred after the application upgrade, indicating a regression in validation behavior. This issue has been resolved, and now IBM Cognos Analytics validation works correctly with valid connection details. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ovaledge.com/hotfix-releases/release7.2.5.x/release7.2.5.9.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.