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

# Release7.2.4.6

This release introduces fixes across Query Sheet, Data Catalog, and User Management modules, improving data accuracy, query behavior, and user association visibility.

**Key Highlights**

* **Query Sheet Schema Mismatch:**
  * Resolved schema validation to allow or restrict multi-schema queries based on system settings and crawled schemas.
* **Synapse Nullable Fields Display:**
  * Resolved an issue where fields in specific tables were shown as NOT NULL despite containing NULL values.
* **Custom Views Temporary Objects:**
  * Resolved an issue where temporary objects were visible in custom views created before migration.
* **User and Team Association Display:**
  * Resolved an issue where users were shown as associated with teams due to legacy team data.

**Release Details:**

<table><thead><tr><th width="145.666748046875">Release Type</th><th width="160">Release Version</th><th width="347.666748046875">Build &#x3C;Release. Build Number. Release Stamp></th><th width="137.3333740234375">Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.4.6</td><td>Release7.2.4.6.724684e7456</td><td>20th Jan 2026</td></tr></tbody></table>

## Query Sheet

### Fixed

**Query Sheet Schema Mismatch**

In the **Query Sheet** module, an issue occurred where a schema mismatch error was shown when queries used tables from different schemas, even when the system setting allowed multiple schemas. The issue has been resolved by applying the schema restriction rule correctly based on the system settings and crawled schemas. Now queries behave as expected when using one or multiple schemas.

## Data Catalog

### Fixed

**Data Catalog Synapse Nullable Fields**

In the **Data Catalog** module, an issue occurred where all fields in specific tables of Azure Synapse were shown as NOT NULL, even though many fields contained NULL values. The issue has been resolved, and now the Data Catalog correctly shows NULL and NOT NULL fields.

**Data Catalog Custom Views Temporary Objects**

In the **Data Catalog** module, an issue occurred where temporary objects were visible in custom views created before migration. The issue has been resolved by applying the correct filter after migration. Now, temporary objects are no longer shown in custom views, and the view behavior is consistent after migration.

## User Management

### Fixed

**User and Team Association Display**

In the **User Management** module, an issue occurred where users were shown as associated with teams due to legacy team data. The issue has been resolved, and now the Users tab shows accurate team associations.

***

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