> 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/release7.2/hotfix-releases/release7.2.5.x/release7.2.5.1.md).

# Release7.2.5.1

This release introduces fixes across Data Catalog, Advanced Tool, Advanced Jobs, Connectors, and Lineage modules, improving performance, stability, and overall system reliability.

**Key Highlights**

* **Generate GUID Advanced Job**
  * Improved job execution performance to ensure the GUID generation job completes within a reasonable duration.
* **LITAT Advanced Job**
  * Enhanced memory handling to prevent execution failures in environments with large lineage data.
* **Detailed Report Download with Report Name Filter**
  * Fixed an issue where detailed report downloads returned empty files when filters were applied.
* **Impacted Object Count Display**
  * Corrected the impacted object count to accurately display zero after lineage removal and reanalysis.
* **Qlik Sense Crawling Failures**
  * Improved crawling stability to ensure consistent metadata processing and lineage generation.
* **Amazon DMS Lineage Display**
  * Resolved lineage display to ensure schema names appear accurately without special character issues.
* **Qlik Sense Lineage Mapping**
  * Fixed incorrect upstream lineage mappings to ensure only valid relationships are shown.
* **Qlik Sense Report Column Lineage**
  * Enhanced lineage resolution to correctly handle aliases for measures and dimensions.

**Release Details:**

<table><thead><tr><th width="140.333251953125">Release Type </th><th width="152.66650390625">Release Version</th><th width="349.3333740234375">Build &#x3C;Release. Build Number. Release Stamp></th><th>Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.5.1</td><td>Release7.2.5.1.7251222244c</td><td>2nd Feb 2026</td></tr></tbody></table>

## Data Catalog

### Fixed

**Detailed Report Download with Report Name Filter**

In the Report Column module, an issue occurred where downloading the detailed report after applying a report name filter generated an empty file despite the job completing successfully. The issue has been resolved, and now the detailed report download correctly includes the expected data when filters are applied.

## Advanced Tool

### Fixed

**Impacted Object Count Display**

In the Impact Analysis module, an issue occurred where the impacted object count did not display zero after lineage was removed and the analysis was rerun. The issue has been resolved, and now the impacted object count accurately displays zero when no impacted objects exist.

## Advanced Jobs

### Fixed

**Generate GUID Advance Job**

In the advanced jobs module, an issue occurred where the Generate GUID job took an unexpectedly long time to complete in a customer environment. The issue has been resolved through execution optimization and improved processing logic. Now the job completes within a reasonable duration.

**LITAT Advanced Job**

In the advanced jobs module, an issue occurred where the LITAT job encountered out-of-memory errors during execution in environments with large lineage data. The issue has been resolved by improving memory handling and execution stability. Now the job completes successfully without failures.

## Connectors

### Fixed

**Qlik Sense Crawling Failures**

In the Qlik Sense (On-Prem) connectors, an issue occurred where crawling failed inconsistently across multiple streams, blocking lineage generation. The issue has been resolved by enhancing crawling reliability and adding better failure handling. Now, crawling completes successfully with improved visibility.

**Amazon DMS Lineage Display**

In the Amazon DMS Connectors, an issue occurred where percentage symbols appeared in schema names after lineage was built. The issue has been resolved by handling special characters correctly. Now schema names display accurately in lineage views.

## Lineage

### Fixed

**Qlik Sense Lineage Mapping**

In the Qlik Sense lineage module, an issue occurred where unrelated tables were incorrectly mapped in the upstream lineage view. The issue has been resolved by correcting how script information is captured. Now lineage accurately reflects correct relationships.

**Qlik Sense Report Column Lineage**

In the Qlik Sense reporting module, an issue occurred where lineage was not built correctly for certain measures and dimensions due to alias usage. The issue has been resolved by enhancing lineage logic to correctly interpret aliases. Now upstream lineage is accurately displayed.

***

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/release7.2/hotfix-releases/release7.2.5.x/release7.2.5.1.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.