# Release7.2.5.13 This release introduces bug fixes across Tags, Data Catalog, Data Products, Business Glossary, Service Desk Administration, Data Quality, Query Sheet, Lineage, Connectors, Governance Roles, and Advanced Jobs. **Key Highlights** * **Tags:** Resolved missing associated resources on the Tags Summary page after upgrade, ensuring tag associations display correctly for all tagged objects. * **Data Catalog:** * Fixed incorrect validation behavior while removing personal default views for MWDW Author users. * Corrected incorrect NOT EQUAL filter behavior for “No Parent Report” values in Reports. * Fixed Simple Download exports ignoring Domain, Category, and Sub Category filters. * **Data Products:** * Fixed Reset Credential handling for connectors using Remote System Permissions by enforcing re-authentication for all users after credential reset. * Resolved missing Object Title values in downloaded Elasticsearch Data Product templates. * **Business Glossary:** * Fixed Detailed Template download failures caused by exceptions when using the Not Equal domain filter condition. * Resolved Steward assignment failures while updating governance ownership for domains. * **Service Desk Administration:** Corrected missing field values during the Approval phase to ensure submitted request details display correctly without additional interaction. * **Data Quality:** Fixed scheduled Data Quality custom SQL rules not executing despite active schedules, ensuring rules execute consistently based on configured schedules. * **Query Sheet:** * Preserved multi-line SQL formatting between Query Sheet and Data Catalog to improve readability and maintenance. * Added support for SQL comments at the beginning, inline, and end of queries. * **Lineage:** * Removed temporary tables from ADF lineage generation for Bedrock integration pipelines to improve lineage accuracy. * Corrected incorrect column mappings generated from aggregate functions used with CASE statements. * **Connectors:** * Fixed Oracle BI Publisher Crawl/Profile failures caused by SOAP response namespace mismatches. * Corrected inconsistent Data Access license add-on display behavior in DBT Core connectors using the S3 repository type. * Resolved Denodo crawl failures after SSL certificate updates by correcting SSL handling and configuration persistence. * **Governance Roles:** Fixed missing default Governance Role assignments for existing Domains and Terms after enabling Governance Roles 4, 5, and 6, ensuring consistent governance role visibility across existing and new objects. * **Advanced Jobs:** Fixed duplicate DBT Advanced Job creation during upgrades, ensuring only valid DBT job configurations remain active. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.13Release7.2.5.13.725132c8237fMay 15, 2026
## Tags ### Fixed **Resolved Missing Associated Resources in Tags Summary Page** In Tags, an issue where associated resources were not visible on the Tags Summary page after upgrading from version 7.2.5.7 to 7.2.5.10 has been resolved. The tag association display logic has been corrected to properly load and display associated resources after the upgrade. Associated objects are now visible correctly for all tags. ## Data Catalog ### Fixed **Resolved Incorrect NOT EQUAL Filter Behavior for Parent Report Field** In Data Catalog Reports, an issue where the NOT EQUAL (≠) filter did not correctly exclude records with the value “No Parent Report” has been resolved. The EQUAL (=) filter returned the correct results, but the NOT EQUAL (≠) condition still included records from the “No Parent Report” category, resulting in inaccurate filtering behavior. The filter-handling logic has been corrected to properly exclude records with the selected value when using the NOT EQUAL condition. **Resolved Simple Download Ignoring Domain, Category, and Sub Category Filters** In Data Catalog list pages, an issue in which the Simple Download feature ignored filters applied to the Domain, Category, and Sub Category fields has been resolved. When the “Equals to & Any of” filter condition was applied with values such as No Domain, No Category, or No Sub Category, only the filtered records were displayed. However, the Simple Download feature exported the entire dataset rather than the filtered results. The download filtering logic has been corrected to ensure the selected filters are applied consistently during export. The Simple Download feature now exports only the filtered records that match the applied filter conditions. ## Data Products ### Fixed **Resolved Reset Credential Reauthentication Issue for Remote System Permissions** In Data Products and Query Sheet, an issue where the Reset Credential action did not retrigger authentication for Author and Viewer users has been resolved. The issue occurred when the connector was configured with the Application follows Remote system permissions setting. After an Admin user triggered the Reset Credential action, previously authenticated Author and Viewer users could still access the source data without re-authentication. The session handling and credential reset logic have been corrected to invalidate existing user sessions after a credential reset. All users are now required to re-authenticate before accessing source data. **Resolved Missing Object Title in Downloaded Data Product Template** In the Data Products, an issue where the Object Title field was missing in downloaded templates has been resolved. Previously, when users filtered records by the Data Product object type and downloaded the template, the exported file did not include the Object Title information, making it difficult to identify the downloaded records correctly.. The template export handling has been corrected to ensure the Object Title field is included in downloaded templates. ## Business Glossary ### Fixed **Resolved Exception During Detailed Template Download with Not Equal Domain Filter** In Business Glossary, an issue where downloading the detailed template generated exceptions in the job logs when users applied the Not Equal filter condition on the Domain field has been resolved. Exceptions were generated during the export process when glossary records were filtered using the Not Equal condition. The filter processing and download handling logic have been corrected to properly support the Not Equal condition during template generation. **Resolved Error While Assigning Steward to Domain** In Business Glossary, an issue where assigning a Steward to the Tax domain failed has been resolved. Updating the Steward field displayed an error pop-up and prevented successful assignment. The domain update handling has been corrected to properly process Steward assignments. Steward values can now be assigned and updated successfully. ## Service Desk Administration ### Fixed **Resolved Missing Field Values in Service Desk Approval Phase** In Service Desk Administration, an issue where field values were not visible during the Approval phase after request creation has been resolved. Submitted field values did not appear correctly in the approval view and were visible only after double-clicking the field. After saving, the values disappeared again. The field rendering and approval page display logic have been corrected to properly display entered field values during the Approval phase. ## Data Quality ### Fixed **Resolved Scheduled Data Quality Rules Not Executing** In Data Quality, an issue where some active custom SQL rules were not executing despite having active schedules has been resolved. Certain rules stopped executing for several months even though the rules, schedules, and job configurations remained active. No visible execution errors were reported, resulting in missed data quality validations. The scheduled rule execution handling has been corrected to properly trigger active Data Quality rules based on their configured schedules. Scheduled custom rules now execute consistently and appear correctly in the execution history. ## Query Sheet ### Fixed **Resolved SQL Formatting Loss Between Query Sheet and Data Catalog** In the Query Sheet and Data Catalog, an issue where formatted SQL queries were saved as single-line queries has been resolved. Queries written in a multi-line, formatted structure in the Query Sheet appeared as single-line SQL statements when saved and opened from the Data Catalog, reducing readability and making troubleshooting difficult. The query save-and-retrieval handling has been corrected to preserve the original SQL formatting. Multi-line formatting and alignment are now retained correctly in Data Catalog. **Resolved SQL Comment Handling in Query Sheet** In the Query Sheet, an issue where SQL comments were not handled correctly in all positions within a query has been resolved. Queries containing SQL comments at the beginning of the query or inline with column definitions failed during execution, while comments added at the end of the query worked correctly. The query parsing and execution handling have been corrected to consistently support SQL comments in all valid positions within a query. ## Lineage ### Fixed **Resolved Temporary Tables Appearing in ADF Lineage** In the ADF connector, an issue where temporary tables were incorrectly captured during lineage generation for complex integration pipelines has been resolved. Temporary tables used during pipeline processing were included in the lineage flow alongside the actual source and target objects, resulting in an inaccurate lineage representation. The lineage processing logic has been corrected to exclude temporary tables from lineage generation. Lineage views now display only relevant source and target objects. **Resolved Incorrect Column Mapping with Aggregate Functions and CASE Statements** In Lineage, an issue where extra columns were incorrectly mapped when aggregate functions were used with CASE statements has been resolved. While building lineage for SQL queries that combine aggregate functions with CASE expressions, the system incorrectly mapped additional columns to unrelated target columns. This resulted in inaccurate column-level lineage and incorrect dependency representation. The lineage parsing and column mapping logic have been corrected to properly process aggregate functions used with CASE statements. Column-level lineage now accurately maps only the expected source and target columns. ## Connectors ### Fixed **Resolved Crawl/Profile Failure in Oracle BI Publisher Connector** In the Oracle BI Publisher connector, an issue where the Crawl/Profile operation failed with an unmarshalling exception has been resolved. Connector validation completed successfully after fixing the proxy attribute, but the Crawl/Profile process failed while processing the SOAP response from the Oracle BI Publisher service due to a namespace mismatch in the getFolderContentsReturn response element. The SOAP response handling logic has been corrected to properly process namespace information. Crawl/Profile operations are now complete successfully without errors. **Resolved Inconsistent License Add-on Display in DBT Core Connector** In the DBT Core connector with the S3 repository type, an issue where the Data Access license add-on was displayed inconsistently between the Add Connector and Edit Connector pages has been resolved. The add-on was not displayed correctly during connector creation, but appeared after reopening the connector in Edit mode. The license add-on display logic has been corrected to ensure consistent behavior across both Add and Edit Connector pages. **Resolved Denodo Crawl Failure After SSL Certificate Update** In the Denodo connector, an issue where crawl jobs failed with SSL certificate errors after configuring a new SSL certificate has been resolved. Connector validation completed successfully after the certificate update, but crawl jobs failed during execution with SSL-related errors. Additionally, the SSL Enabled flag did not persist correctly in the Production environment and automatically reverted to False after saving. The SSL handling and connector configuration logic have been corrected to ensure the SSL Enabled setting is retained and SSL certificate configurations are applied consistently during crawl execution. Denodo crawl jobs are now complete successfully without SSL certificate failures. **Resolved Unauthorized Power BI Report Preview Access** In Data Catalog, an issue that allowed users to preview Power BI reports in OvalEdge without access to the Power BI portal has been resolved. Users without backend access to the report could open and view it directly from the Report Preview page without authentication or access validation. Normally, users should receive a sign-in prompt and be allowed to view reports only after successful authentication and access verification. The report preview access validation logic has been corrected to properly enforce Power BI authentication and permission checks. Users can now preview reports only if they have the required access in the Power BI portal. ## Governance Roles ### Fixed **Resolved Missing Default Governance Role Assignment for Existing Domains and Terms** In Data Catalog, Governance Roles 4, 5, and 6 appeared blank for existing Domains and Terms after enabling the roles. Newly created objects displayed the roles correctly, but existing objects did not update automatically. To resolve this issue, a new advanced job named **Update Blank Governance Roles** has been added. Running this job fills blank Governance Roles 4, 5, and 6 in existing crawled assets with the principal admin user configured during the initial connection setup. ## Advance Jobs ### Fixed **Resolved Duplicate DBT Advanced Job Creation After Upgrade** In Advanced Jobs, an issue where duplicate “DBT File Parse And Update Description” jobs were created after the upgrade has been resolved. During the investigation, two DBT Advanced Jobs with the same configuration were identified in the environment. One job contained a long execution history and was identified as the original job, while the second duplicate job appeared after the recent OvalEdge upgrade and contained only a few executions. This caused duplicate DBT Advanced Job entries and created confusion in job management and execution tracking. The upgrade handling logic has been corrected to prevent duplicate DBT Advanced Job creation during upgrades. Existing duplicate jobs have been identified and handled appropriately, ensuring only valid job configurations remain active. *** 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.13.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.