> 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.17.md). # Release7.2.5.17 This release introduces key enhancements and bug fixes across Data Catalog, Data Classification Recommendations, Lineage, Compare Schema, Security, and Connectors, improving metadata management, recommendation performance, lineage accuracy, schema comparison reliability, data protection, and connector stability. **Key Highlights** * **Login**: Fixed an issue where the SSO login page displayed incorrectly on Windows systems after migration. * **Data Catalog**: Fixed download failures for temporary lineage tables and corrected the Has Lineage filter behavior to ensure accurate search results in the Temp Lineage Objects system view. * **Data Classification Recommendations**: Improved page performance for large recommendation sets by reducing load times, enabling faster selections, supporting multi-page bulk actions, and preserving selections across navigation and filters. * **Lineage (Tableau)**: Resolved a report-level lineage loading issue that prevented lineage information from displaying, ensuring report lineage is now available in the Data Catalog. * **Security**: Added database-level encryption for information stored within the platform, providing stronger protection for sensitive data retained across supported components. * **Connectors** * **Delta Lake**: Fixed connector validation to prevent false health check failures and unnecessary crawl job interruptions when Databricks clusters are temporarily inactive. * **ADF**: Resolved memory-related crawling failures, enabling successful metadata collection for large workloads. * **Power BI**: Fixed incorrect lineage mappings by linking Power BI assets to original Dremio tables and views instead of temporary objects. * **Informatica PowerCenter**: Resolved lineage generation failures caused by existing temporary connections, ensuring lineage processes complete successfully. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.17Release7.2.5.17.725171b8f35bMay 05, 2026
## Login ### Fixed **Fixed SSO Login Page Display Issue on Windows After Migration** In Authentication, an issue in which the SSO login page was displayed incorrectly on Windows systems after an upgrade has been resolved. The issue affected the appearance and functionality of the login page for Windows users, while the same page displayed correctly on macOS systems. A JavaScript-related UI rendering issue caused the problem. After the migration, the login page has been updated to ensure a consistent, correct display across supported operating systems. ## Data Catalog ### Fixed **Fixed Download Failure for Temporary Lineage Tables** In Data Catalog, an issue where temporary lineage tables could not be downloaded from the Temp Lineage Objects system view has been resolved. The download functionality (Simple Download) has been fixed to ensure all temporary lineage tables can be downloaded successfully in CSV. **Fixed Lineage Filter Behavior in Temp Lineage Objects** In Data Catalog, an issue where objects in the Temp Lineage Objects (System View) with lineage appeared in the search results when the 'Has Lineage' filter was set to 'No' has been resolved. The filter incorrectly included objects that already had lineage information, causing inconsistent results. The filter logic has been corrected to display only objects without lineage. ## Data Classification Recommendations ### New & Improved **Improved Performance and Bulk Actions in Data Classification Recommendations** The Data Classification Recommendations page experienced performance issues when processing a large number of recommendations. Users experienced long page load times, and selecting a checkbox often took several seconds to respond, making it difficult to manage recommendations efficiently. Performance has improved, with the page now loading faster and checkbox selections responding immediately. Top Values information is now displayed only when requested through a View Profile option, reducing delays and improving overall performance. Users can also select recommendations across multiple pages, and their selections remain available as they navigate or apply filters. A selection banner displays the total number of selected items and provides an option to clear all selections. ## Lineage ### Fixed **Fixed Report-Level Lineage Display Issue** In Tableau, an issue where the report-level lineage page remained stuck in a loading state and did not display lineage information in the Data Catalog has been resolved. The issue was fixed to ensure report-level lineage loads correctly and displays the expected lineage information. ## Security ### New & Improved **Data Encryption for Information Stored in the Database** Information stored in the OvalEdge database, including data collected through profiling and other platform activities, was previously saved without encryption, leaving sensitive information unprotected. With this enhancement, data stored in the OvalEdge database is now encrypted to help protect sensitive information. The encryption applies to data retained across supported platform components, providing stronger protection for information stored within the system. The system setting (oe.source.data.encryption.enabled) controls the encryption of source data fields. ## Connectors ### Fixed **Resolved Incorrect Delta Lake Connector Validation Failures** In Delta Lake Connection, an issue where automatic connector validation incorrectly marked the connector as unavailable when the Databricks cluster was inactive has been resolved. When the cluster was temporarily inactive, automatic validation failed, changing the connector health status to Red and causing scheduled crawl jobs to fail. Manual validation continued to work successfully. The validation process has been improved to handle temporary cluster inactivity more effectively, preventing incorrect changes to connector health status and unnecessary crawl job failures. **Resolved Memory Issue in ADF Crawling** In ADF Connector, an issue in which the connector failed to crawl due to insufficient memory during processing has been resolved. The crawl stopped before metadata collection was completed, preventing the full ingestion of information from ADF. The crawling process has been improved to handle large workloads more efficiently, allowing metadata collection to complete successfully. **Resolved Incorrect Lineage Mapping for Dremio Sources** In Power BI, an issue where automatic lineage linked reports and datasets to temporary objects instead of the original Dremio tables and views has been resolved. This issue caused incomplete and inaccurate lineage, making it difficult to trace data from Power BI reports back to the correct source objects. The lineage process has been updated to identify and connect Power BI assets to the original Dremio tables and views, ensuring accurate end-to-end data traceability. **Fixed Lineage Generation Issue in Informatica PowerCenter** In Informatica PowerCenter, an issue where lineage generation failed due to a temporary connection already existing has been resolved. The lineage process stopped with an error when it encountered an existing temporary connection, preventing lineage from being generated. The process has been updated to correctly handle temporary connections, allowing lineage generation to complete successfully. *** 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.17.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.