# Release7.2.5.14 This release introduces bug fixes across Tags, Data Catalog, Business Glossary, Lineage, and Connectors. **Key Highlights** * **Data Catalog:** Resolved rich text editor issues affecting hyperlinks, tables, bullet lists, and formatted content in Business Description and Technical Description fields. Improved paragraph formatting controls and corrected table editing behavior. * **Business Glossary:** Fixed description generation failures for Terms that displayed “Question length is too long” errors. Corrected hyperlink formatting behavior in generated descriptions. * **Lineage:** * **QlikSense:** Improved QlikSense upstream lineage generation by correcting SQL parsing and query status handling for “Success Temp Lineage” scenarios. * **ADF Lineage:** Corrected column-level lineage generation to exclude conditional and helper columns used only in CASE statements, filters, and intermediate logic. * **Connectors:** * **QlikSense Connectors:** Fixed Metadata Export Service issues that caused incomplete metadata retrieval during advanced job execution. * **QlikSense Crawl/Profile:** Resolved continuous page reload issues and corrected report group loading behavior during crawl and profile operations. Added additional logging for troubleshooting. * **SAP BODS Connector:** Fixed dialect configuration save failures for Oracle and SQL dialects from the connector settings page. Release Details:
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.14Release7.2.5.14.725142ba5824May 20, 2026
## Data Catalog ### Fixed **Rich Text Editor Formatting Issues** In Data Catalog, multiple issues related to the Business Description and Technical Description fields in the rich text editor have been resolved. Hyperlinks added using links or @mentions were converted to plain text after saving. Editing content that contained tables, bullet lists, or formatted text removed the existing formatting and displayed the content as plain text. Clicking inside tables also highlighted table borders unexpectedly, and the More Paragraph option in the editor toolbar did not open additional paragraph formatting controls. The rich text editor handling has been corrected to retain hyperlinks, tables, bullet lists, and formatted content after saving. The More Paragraph option now opens additional paragraph formatting controls such as line height, paragraph style, text direction, and indent options. Table editing behavior has also been corrected to prevent unwanted table border highlighting. ## Business Glossary ### Fixed **Resolved Description Generation Issue for Terms** In Business Glossary, an issue where Business Description and Data Description generation for Terms displayed a “Question length is too long” error message has been resolved. The description generation process has been corrected for the Term Business Description and Data Description fields. Hyperlink formatting in generated descriptions now works correctly, including support for bold formatting. ## Lineage ### Fixed **Resolved QlikSense Lineage Build Issue** In QlikSense lineage processing, an issue that caused incomplete upstream lineage generation for codes with the status “Success Temp Lineage” has been resolved. Some SQL queries failed during parsing, while other queries displayed empty status values. This behavior caused the incomplete generation of upstream lineages for the QlikSense code. The lineage parsing and query-processing logic have been corrected to handle these SQL scenarios properly and generate upstream lineage accurately. **Improved ADF Column-Level Lineage Processing** In ADF lineage generation, an issue where columns used only in CASE conditions, filters, and helper logic were included as direct contributors to target columns has been resolved. Conditional and helper columns were included in the final column-level lineage output, resulting in incorrect lineage relationships. The lineage processing logic has been improved to distinguish between columns that contribute to final output values and those used only for conditional or filtering logic. Helper columns are no longer incorrectly included in the final lineage output. ## Connectors ### Fixed **Resolved QlikSense Metadata Export Service Issue** In QlikSense, an issue in which the Metadata Export Service advanced job retrieved incomplete or inaccurate metadata has been resolved. The advanced job completed successfully, and connectivity, SSL communication, authentication, and QRS API validation worked correctly. However, the exported metadata did not contain the expected information. The metadata export handling has been corrected to accurately retrieve and export metadata during advanced job execution. **Resolved QlikSense Crawl/Profile Loading Issue** In QlikSense, an issue where the Crawl/Profile page continuously reloaded and did not display report groups has been resolved. The connector failed to load report groups correctly during crawl and profile operations. The crawl and profile handling process has been corrected to ensure report groups are loaded properly during connector operations. Additional logging has also been added for issue analysis and troubleshooting. **Resolved SAP BODS Dialect Save Issue** In the SAP BODS connector, an issue where an error popup appeared while saving dialect configurations has been resolved. Saving dialect configurations such as Oracle and SQL from the connector settings page displayed an error popup. The dialect configuration handling has been corrected to save configuration changes successfully without displaying errors. *** 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.14.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.