> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/hotfix-releases/release7.2.5.x/release7.2.5.14.md).

# Release7.2.5.14

This release introduces bug fixes across Tags, Data Catalog, Business Glossary, Lineage, and Connectors.&#x20;

**Key Highlights**

* **Data Catalog:** Fixed rich text editor formatting issues in Data Catalog to correctly retain hyperlinks, tables, bullet lists, and formatted content after saving and editing.
* **Business Glossary:** Improved Business Glossary description generation to resolve long question errors and support proper hyperlink and bold text formatting.
* **Lineage:**
  * **QlikSense:** Enhanced Qlik Sense lineage processing to correctly parse SQL queries and generate accurate upstream lineage.
  * **ADF Lineage:** Improved ADF column-level lineage logic to exclude helper and conditional columns from final lineage mappings.
* **Connectors:**&#x20;
  * Fixed Qlik Sense Metadata Export Service to retrieve complete and accurate metadata during Advanced Job execution.
  * Resolved Qlik Sense Crawl/Profile loading issues to correctly display report groups during connector operations.
  * Fixed SAP BODS dialect configuration save issues to allow successful saving of dialect settings without errors.

**Release Details:**

<table><thead><tr><th width="147.4000244140625">Release Type</th><th width="153.800048828125">Release Version</th><th width="348">Build &#x3C;Release. Build Number. Release Stamp></th><th width="163.2000732421875">Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.5.14</td><td>Release7.2.5.14.725142ba5824</td><td>May 20, 2026<br></td></tr></tbody></table>

## Data Catalog

### Fixed

**Resolved 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. Previously, hyperlinks added using links or @ mentions were converted to plain text after saving. In some cases, editing content containing tables, bullet lists, or formatted text removed the existing formatting and displayed the content as plain text.

Additional issues affecting table editing and paragraph formatting controls have also been resolved. The More Paragraph option in the editor toolbar now correctly displays additional formatting controls, including line height, paragraph style, text direction, and indent. Table editing behavior has also been corrected to prevent unwanted table border highlighting.

The rich text editor now retains hyperlinks, tables, bullet lists, and formatted content correctly after saving and editing.

## Business Glossary&#x20;

### 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.&#x20;

The description generation process for the Term Business Description and Data Description fields has been corrected. Hyperlink formatting in generated descriptions now works correctly, including support for bold formatting.

## Lineage&#x20;

### Fixed

**Resolved Qlik Sense Lineage Build Issue**

In Qlik Sense lineage processing, an issue that caused incomplete upstream lineage generation for codes with the status “Success Temp Lineage” has been resolved. Previously, some SQL queries failed during parsing, while others displayed empty query statuses, resulting in incomplete upstream lineage generation for Qlik Sense scripts.

The lineage parsing and query-processing logic have been corrected to properly handle these SQL scenarios and accurately generate upstream lineage.

**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&#x20;

### Fixed

**Resolved Qlik Sense Metadata Export Service Issue**

In Qlik Sense, an issue where the Metadata Export Service Advanced Job retrieved incomplete or inaccurate metadata has been resolved. Previously, the advanced job completed successfully, but 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 Qlik Sense Crawl/Profile Loading Issue**

In Qlik Sense, an issue where the Crawl/Profile page continuously reloaded and did not display report groups has been resolved. Previously, report groups were not loaded correctly during crawl and profile operations.

The crawl and profile handling process has been corrected to ensure report groups load properly during connector operations. Additional logging has also been added to support issue analysis and troubleshooting.

**Resolved SAP BODS Dialect Save Issue**

In the SAP BODS connector, an issue where an error pop-up appeared while saving dialect configurations has been resolved. Previously, saving dialect configurations, such as Oracle and SQL, from the connector settings page displayed an error message.

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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/hotfix-releases/release7.2.5.x/release7.2.5.14.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
