> 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.22.md).

# Release7.2.5.22

This release introduces key enhancements across Data Catalog, Data Products, Data Quality Rules, Lineage, Connectors, and Advanced Jobs, improving metadata management, governance administration, data quality reliability, lineage accuracy, connector capabilities, and platform integration.       &#x20;

**Key Highlights**

* **Data Catalog**: Fixed an issue that prevented formulas from being copied from Power BI report tooltips, enabling easier review, reuse, and validation of formula logic.
* **Data Products**: Expanded administrative capabilities by allowing Principal Admin and Data Domain Admin roles to manage Data Products without requiring governance role assignments, and introduced a new Search Data Products API with advanced filtering, sorting, pagination, and optional related object retrieval.
* **Data Quality Rules**: Resolved custom rule execution failures and fixed formatting issues in custom fields, ensuring reliable rule execution and clean, consistent content when pasting text.
* **Lineage (Oracle)**: Corrected table-level and column-level lineage mappings by eliminating invalid relationships and accurately capturing supported table and column dependencies.
* **Connectors**: Added branch-specific crawling for the Power BI PBIP Connector, expanded the HubSpot Connector to support Line Items and Project Records, enabled synchronization of business descriptions from OvalEdge to Denodo, improved profiling reliability for the Sybase ASE Connector, and enhanced Delta Lake Connector validation to prevent false connector health failures during temporary Databricks cluster inactivity.&#x20;
* **Advanced Jobs**: Optimized security-related database tables by removing redundant indexes, reducing database size and improving performance. Run the **Create Security ACL Entries** Advanced Job after upgrading to apply the updated database structure.

**Release Details:**

<table><thead><tr><th width="136.3333740234375">Release Type</th><th width="151.4444580078125">Release Version</th><th width="345.5555419921875">Build &#x3C;Release. Build Number. Release Stamp></th><th width="131.5555419921875">Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.5.22</td><td>release7.2.5.22.72522d71ad5f</td><td>July 22, 2026</td></tr></tbody></table>

## Data Catalog

### Fixed

**Resolved Formula Copy Issue in Power BI Reports**&#x20;

In Data Catalog | Power BI reports, an issue where formulas displayed in the Formula field tooltip could not be copied has been resolved.

The tooltip now supports copying the complete formula, making it easier to reuse, review, share, and validate formula logic.

## Data Products

### New & Improved

**Expanded Data Product Management Permissions for Administrative Roles**

Certain Data Product management tasks, such as updating governance roles, modifying Data Product Managers, and changing Data Product lifecycle states, could only be performed by assigned governance roles. This required administrators to depend on individual role assignments, which could delay urgent updates.

With this enhancement, Principal Admin (OE Admin) and Data Domain Admin roles now have full Data Product management permissions. These administrators can perform all Data Product administration and configuration activities without being assigned as a Data Product Manager, Business Owner, Steward, or Custodian, while the existing permissions for all other governance roles remain unchanged.

**Search Data Products Using API**

Retrieving Data Products through APIs offered limited search capabilities, making it difficult to locate specific Data Products or retrieve only the required information. Users often had to process larger result sets or make additional requests to gather related details.

With this enhancement, a new Search Data Products API enables users to search and retrieve Data Products using a wide range of filters, including name, Data Domain, status, access type, delivery access mode, governance roles, tags, criticality, and sensitivity. The API also supports sorting, pagination, and optional inclusion of related information such as Data Objects, Data Contracts, Custom Fields, and Related Objects.

## Data Quality Rules

### Fixed

**Resolved Custom Data Quality Rule Execution Failures**&#x20;

In Data Quality Rules, an issue where multiple custom data quality rules failed with an Execution Failed status has been resolved. Several custom rules that had previously run successfully stopped executing and consistently failed during validation.&#x20;

The execution process has been corrected to ensure custom data quality rules run successfully and report accurate results.

**Resolved Formatting Issues in DQR Custom Fields**&#x20;

In Data Quality Rules, an issue where pasting text into custom fields added unwanted formatting and blank spaces has been resolved.

Text copied from sources such as Microsoft Word, Notepad, or other application pages no longer includes extra formatting when pasted into DQR custom fields, ensuring clean and consistent content.

## Lineage

### Fixed

**Resolved Incorrect Oracle Lineage Mappings**&#x20;

In Oracle Lineage, an issue where table-level and column-level lineage included incorrect relationships and missed valid data mappings has been resolved.&#x20;

Lineage no longer creates relationships for invalid columns and now accurately captures valid table and column mappings across supported queries and package bodies.

## Connectors

### New & Improved

**Branch Selection Support for Power BI PBIP Connector**

The Power BI PBIP connector crawled reports from Azure DevOps repositories without considering the repository branch. When the same report existed in multiple branches, such as development and production, it could result in duplicate report discovery or metadata being extracted from the wrong version.

With this enhancement, the PBIP connector now supports branch-specific report crawling for Azure DevOps repositories. Users can configure the connector to crawl reports from the required branch, ensuring that only the intended version of a report is processed for metadata extraction.

**Expanded HubSpot Connector Support for Line Items and Project Records**

The HubSpot connector supported crawling and profiling only the core CRM objects, such as Companies, Contacts, Deals, Products, and Tickets. As a result, Line Items and Project Records were not available for cataloging or governance in OvalEdge.

With this enhancement, the HubSpot connector now supports crawling and profiling of Line Items and Project Records. These objects are discovered and cataloged alongside the existing HubSpot objects, providing a more complete view of CRM data.

**Synchronize Business Descriptions from OvalEdge to Denodo**

Business descriptions maintained in OvalEdge were not automatically synchronized with Denodo. As a result, table and column descriptions had to be updated separately, leading to inconsistent metadata and additional manual effort.

With this enhancement, OvalEdge can synchronize business descriptions for tables and columns to the corresponding descriptions in Denodo through an Advanced Job. This keeps metadata consistent across both platforms without requiring manual updates.

### Fixed

**Resolved Partial Profiling Results in Sybase ASE Connector**&#x20;

In the Sybase ASE Connector, an issue where profiling completed with partial results for some database objects has been resolved. Profiling failed for certain tables even though connection validation and metadata crawling completed successfully.&#x20;

The profiling process has been updated to improve query handling, ensuring more reliable and complete profiling results.

**Resolved False Connector Health Failures**&#x20;

In the Delta Lake Connector, an issue where automatic connector validation marked the connector as unhealthy when the Databricks cluster was temporarily inactive has been resolved. Automatic validation incorrectly changed the connector health status to Red, causing scheduled crawl jobs to fail, even though manual validation completed successfully.

The validation process has been improved to better handle temporary cluster inactivity and prevent unnecessary connector health failures.

## Advanced Jobs

### New & Improved

Database Optimization for Security Tables

Over time, the security-related database tables accumulated redundant indexes, increasing database size and affecting overall performance. Maintaining these unnecessary indexes also added storage overhead.

With this enhancement, the database has been optimized by removing redundant indexes from the security tables, reducing database size and improving performance. To apply the updated database structure, run the **Create Security ACL Entries** Advanced Job after upgrading.

***

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.22.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.
