> 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.21.md). # Release7.2.5.21 This release introduces bug fixes across Data Products, Business Glossary, Lineage, Impact Analysis, Load Metadata from Files, Connectors, and Audit Trails, improving metadata accuracy, lineage reliability, filtering behavior, import processing, log management, and audit reporting. **Key Highlights** * **Data Products**: Fixed an incorrect error message displayed during asset association, ensuring successful asset additions now show an accurate success notification. * **Business Glossary**: Resolved missing column headers in the Add Related Objects pop-up, improving navigation and related term selection. * **Lineage**: Fixed Power BI Cloud SQL extraction and source code processing issues, enabling successful lineage generation for dataflows and all Power BI source code. * **Impact Analysis**: Fixed the Responsible Code filter behavior and impacted object tag display, ensuring accurate filtering results and metadata visibility. * **Load Metadata from Files**: Fixed Business Glossary metadata import failures caused by text-length validation, enabling successful updates to long descriptions and Business Rule values. * **Connectors**: Optimized Bridge log file management to control log growth, reduce storage usage, and improve operational stability. * **Audit Trails**: Resolved incomplete AI audit trail downloads by ensuring all records matching the applied filters are included, regardless of pagination settings. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.21release7.2.5.21.7252136b0fe2July 13, 2026
## Data Products ### Fixed **Fixed Incorrect Message During Asset Association** In Data Products, an issue where adding multiple assets displayed an incorrect error message even though all selected assets were successfully associated has been resolved. The notification now accurately reflects the association result and displays a success message when all selected assets are added successfully. ## Business Glossary ### Fixed **Resolved Missing Column Headers in Related Objects Pop-up** In Business Glossary, an issue where column headers were not visible in the Add Related Objects pop-up has been resolved. Search fields were displayed in place of column headers, making it difficult to identify and select the correct related terms. The pop-up now displays the column headers correctly, improving navigation and term selection. ## Lineage ### Fixed **Resolved Power BI Cloud SQL Extraction Issue** In Power BI Cloud, an issue where SQL queries were not fully extracted from dataflow expressions, causing lineage parsing to fail for some datasets, has been resolved. The SQL extraction process has been corrected to capture complete queries, enabling successful lineage generation for the affected datasets. **Resolved Power BI Source Code Lineage Failure** In the Power BI Connector, an issue in which building lineage for all source code failed and no lineage was generated has been resolved. The lineage job completed with an error and did not produce the expected results. The processing has been updated to build lineage for all source code successfully. ## Impact Analysis ### Fixed **Resolved Responsible Code Filter Issue in Impact Analysis** In Advanced Tools | Impact Analysis, an issue in which the Responsible Code filter did not return the correct results for the Empty and Not Empty conditions in the Impacted Objects tab has been resolved. The filter now correctly displays impacted objects based on whether a responsible code is present. **Resolved Incorrect Tags in Impacted Objects** In Impact Analysis, an issue in which impacted objects displayed tags from the source object instead of their own has been resolved. The tag display has been corrected to show the tags associated with each impacted object, ensuring accurate metadata is displayed. ## Load Metadata from Files ### Fixed **Business Glossary Metadata Import Fix** In Advanced Tools | Load Metadata from Files, an issue where Business Glossary updates failed during metadata import due to text length validation has been resolved. Business Glossary files containing long descriptions or existing Business Rule values may cause validation errors and prevent updates. The import process now correctly handles these values and updates the metadata successfully. ## Connectors ### Fixed **Optimized Bridge Log File Management** In Connectors, an issue where log files grew excessively during bridge operations, consuming large amounts of storage and affecting normal processing, has been resolved. The logging configuration has been updated to manage log file size and cleanup better, helping prevent excessive storage usage during bridge operations. ## Audit Trails ### Fixed **Resolved Incomplete AI Audit Trail Downloads** In Audit Trails, an issue where downloads from the AI tab did not include all available records has been resolved. Downloaded files contained only a portion of the available data, and the number of exported records varied based on the selected page size. The download process has been updated to export all records that match the applied filters, regardless of the pagination setting. *** 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.21.md?ask=&goal= ``` `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.