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

# Release7.2.5.26

This release introduces bug fixes across Business Glossary and Connectors, improving metadata consistency and connector management reliability.         &#x20;

**Key Highlights**

* **Business Glossary**: Fixed an issue where deleted auxiliary business terms continued to appear as associated terms for tables, ensuring term associations remain consistent between Security and Data Catalog.
* **Connectors (Power BI)**: Resolved a connector deletion issue related to connection encryption errors, allowing Power BI connectors to be deleted successfully even when their health status is inactive.

**Release Details:**

<table><thead><tr><th width="135">Release Type</th><th width="153.3333740234375">Release Version</th><th width="345">Build&#x3C;Release. Build Number. Release Stamp></th><th>Build Date</th></tr></thead><tbody><tr><td>Patch Release</td><td>Release7.2.5.26</td><td>release7.2.5.26.72526.998dc8e</td><td><br>August 24, 2026</td></tr></tbody></table>

## Business Glossary

### Fixed

**Resolved Auxiliary Business Term Association Issue**&#x20;

In Security, an issue where deleted auxiliary business terms continued to appear as associated terms for tables, even after removal from the Data Catalog, has been resolved. The term associations now remain consistent between the Security module and Data Catalog (Tables).

## Connectors

### Fixed

**Resolved Power BI Connector Deletion Issue**&#x20;

In the Power BI Connector, an issue where a connector could not be deleted and displayed an error related to connection encryption has been resolved. The connector can now be deleted successfully, even when its health status is inactive.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
