> 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.32.md). # Release7.2.5.32 This release includes key bug fixes across Business Glossary, Security, and Power BI Connector, improving Datetime column masking, source count accuracy, application security, lineage object resolution, and Paginated Report lineage. **Key Highlights** * **Business Glossary:** * Resolved an issue where Datetime column values remained masked instead of displaying the configured masking value, and actual values were not displayed for roles specified under Allowed Roles. * Resolved an issue where Authoritative Source and Originative Source counts on the Term Details / Summary tab did not match the actual objects associated with the term under the Associated Objects tab. * **Lineage:** * Resolved an issue where lineage used temporary objects instead of available original Azure Synapse objects in the Data Catalog. * Resolved an issue where Paginated Reports were not linked to the correct Shared Dataset when the Dataset ID did not match. The Dataset Path is now used to identify the correct Shared Dataset. * **Security**: * Resolved critical security vulnerabilities in a library that supports application functionality and updated the library to a secure supported version. Release Details:
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Patch ReleaseRelease7.2.5.32release7.2.5.32.72532.f0e08eeOctober 7, 2026
## Business Glossary ### Fixed **Column Masking for Datetime Data Type** In Column Masking, Datetime column values were displayed as masked values instead of the configured masking value when masking policies used Date, String, or Number masking schemas. In addition, actual values were not displayed for roles specified under Allowed Roles. The issue has been resolved, and now the configured masking value is displayed correctly for Datetime columns, and actual values are displayed for the roles specified under Allowed Roles. **Business Glossary Source Counts** In the Business Glossary, the Authoritative Source and Originative Source counts on the Term Details / Summary tab did not match the actual objects associated with the term under the Associated Objects tab. The issue has been resolved, and now the Authoritative Source and Originative Source counts accurately reflect the corresponding objects displayed under the Associated Objects tab. ## Lineage ### Fixed **Power BI | Lineage Using Original Azure Synapse Objects** In the Power BI connector, lineage was built using temporary source objects even when the corresponding original Azure Synapse tables were already available in the Data Catalog. This resulted in duplicate representations of the same source objects and prevented the lineage from linking the Power BI report to the original Azure Synapse objects. The issue has been resolved, and now lineage uses the original Azure Synapse objects available in the Data Catalog instead of creating or using temporary objects for the corresponding source objects. **Power BI | Paginated Report Lineage Using Dataset Path** In the Power BI connector, some Paginated Reports were not linked to their corresponding Shared Dataset because the Dataset ID in the report source code did not match the actual Shared Dataset. Although lineage for the Shared Dataset was generated correctly, the relationship between the Shared Dataset and Paginated Report was missing. The issue has been resolved, and now the Power BI connector uses the Dataset Path to identify and link the correct Shared Dataset when the Dataset ID does not match, allowing complete lineage to be generated from the source through the Shared Dataset to the Paginated Report. ## Security ### Fixed Critical security vulnerabilities were identified in a library that supports application functionality. The issue has been resolved, and now the application uses a secure supported version of the library, addressing the identified vulnerabilities without affecting existing application functionality. *** 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.5.x/release7.2.5.32.md?ask=&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.