> 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.24.md). # Release7.2.5.24 This release introduces key enhancements and bug fixes across Projects, Reference Data Management, Policy Manager, Lineage, Connectors, and Data Access, improving task management, reference creation, policy visibility, lineage accuracy, metadata extraction, and access management. **Key Highlights** * **Projects**: Fixed task date handling to ensure start and end dates are saved and displayed accurately, including when no dates are specified. * **Reference Data Management**: Resolved an issue preventing references from being created in Reference Data Unit business descriptions, ensuring they are correctly linked and displayed. * **Policy Manager**: Restored the visibility of configured custom fields, allowing policy information to be viewed and updated as expected. * **Lineage**: Fixed Azure Data Factory lineage by correctly resolving nested dynamic expressions and enhanced keyword search highlighting to consistently highlight all matching results in lineage code. * **Connectors (Power BI)**: Added support for extracting report columns from Power BI reports published using the .PBIR format, enabling accurate metadata extraction without requiring a Layout file. * **Data Access**: Resolved masking policy management issues by fixing policy removal errors, ensuring consistent schema name display, and eliminating duplicate masking policies from filter lists. **Release Details**:
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.24release7.2.5.24.72524.d647249August 06, 2026
## Projects ### Fixed **Resolved Project Task Date Saving Issue** In Projects, an issue where task start and end dates were not saved correctly has been resolved. Tasks created without dates were automatically assigned default dates, and manually selected future dates were overwritten. The date handling has been corrected to accurately save and display the specified dates, including when no dates are provided. ## Reference Data Management ### Fixed **Fixed Reference Creation in Reference Data Units** In Reference Data Management, an issue in which references added to the business description of Reference Data Units were not created has been resolved. References added using the @ option or the reference selector are now created correctly and appear in the associated asset's References section. ## Policy Manager ### Fixed **Policy Manager Custom Fields Visibility Fix** In Policy Manager, an issue where configured custom fields were not displayed has been resolved. Custom fields are now visible as expected, allowing policy information to be viewed and updated correctly. ## Lineage ### Fixed **Resolved Nested Expression Parsing in Lineage** In Azure Data Factory | Lineage, an issue where nested dynamic expressions were not processed correctly during lineage generation has been resolved. Complex file name expressions were displayed instead of the actual resolved file names, resulting in inaccurate lineage. The parsing logic has been updated to resolve nested expressions and generate accurate lineage correctly. **Fixed Repeated Keyword Highlighting in Lineage** In Data Catalog | Table Column Lineage, an issue where keyword search did not consistently highlight all matching results in code has been resolved. Repeated keywords were not always highlighted, and some matches appeared with inconsistent highlight colors. The search highlighting has been corrected to consistently display all matching keywords. ## Connectors ### New & Improved **Improved Report Column Extraction for Power BI Reports Using the .PBIR Format** The report columns were not extracted for Power BI reports published using the .PBIR format, even when the Report Columns option was enabled for the connector. Since the .PBIR format does not generate a Layout file, OvalEdge could not retrieve report column metadata. With this enhancement, the Power BI connector supports extracting report columns from reports published using the .PBIR format, eliminating the dependency on the Layout file. This enhancement improves metadata extraction for modern Power BI report formats, ensuring report columns are accurately discovered and cataloged in OvalEdge. ## Data Access ### Fixed **Resolved Masking Policy Removal Error** In Data Access Management, an issue where an error occurred while removing a masking policy from table columns has been resolved. The masking policy can now be removed successfully without errors. **Schema Name Display Fixed for Masking Policies** In Data Access Management (DAM), an issue where assigned masking policies did not consistently display the schema name has been resolved. Masking policies assigned through Terms or the Security page showed only the policy name instead of the expected SchemaName.PolicyName format. The display has been updated to show the schema name consistently across all assignment methods. **Resolved Duplicate Masking Policies in Filters** In Data Access Management (DAM), an issue where the Masking Policy filter in Table Columns displayed duplicate policy names and inconsistent selection behavior has been resolved. Masking policies now appear only once in the filter list, and all listed policies can be selected consistently. *** 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.24.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.