> 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.4.x/release7.2.4.2.md).

# Release7.2.4.2

This release introduces key enhancements across Tags and Connectors, improving tag accuracy and Power BI metadata stability.

**Key Highlights**

* **Tags**: Fixed incorrect tag association counts caused by migration issues. Tag counts now display accurately across both the List View and Tree View.
* **Connectors (Power BI)**: Resolved issues with renamed pages causing inactive visuals and ambiguity errors. Updated metadata and page configurations now ensure stable and accurate crawl results.

**Release Details:**

<table><thead><tr><th width="136.1112060546875">Release Type   </th><th width="134.2222900390625">Release Version</th><th width="352.22235107421875">Build &#x3C;Release. Build Number. Release Stamp></th><th>Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.4.2</td><td>Release7.2.4.2.72428104679</td><td>12th Dec 2025</td></tr></tbody></table>

## Tags

### Fixed

**Accurate Tag Counts Restored Across Tag Views**

In Tags, an issue where the direct object association count displayed incorrect values after migration from Release6.3.2.1.3.13 to Release7.2.3 has been fixed.

Tag counts for associated objects, including Reports and Report Columns, appeared incorrectly in both the Tags List View and the Tree View. The migration logic has been corrected, and the tag association counts across all tag views are now accurate.

## Connectors

### Fixed

**Improved Power BI Metadata Handling for Renamed Pages**

In Power BI Metadata Curation, an issue occurred where interchanging page names caused visuals to become inactive and new visuals to be created during the crawl. A log entry indicated that existing chart components were being marked as removed. An additional issue involved ambiguity errors caused by identical column names and column counts across pages, which persisted even after structural updates. The fix included updating page names, adjusting column configurations in the affected subreport, and manually adding the required metadata for subreports, visuals, and pages. Metadata was then validated after republishing and re-crawling.

***

Copyright © 2025, 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 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.4.x/release7.2.4.2.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.