> 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.20.md). # Release7.2.5.20 This release introduces key enhancements and fixes across Data Catalog, Data Classification Recommendations, Reference Data Management, Data Quality Rules, Lineage, Connectors, Security, and Advanced Jobs, improving usability, recommendation accuracy, lineage reliability, connector authentication, access management, and data protection. **Key Highlights** * **Data Catalog (Quickbase)**: Fixed an issue where table-level profiling failed to generate results for Quickbase tables, ensuring profiling now runs successfully and produces the expected statistics. * **Data Classification Recommendations**: Excluded temporary tables from the recommendation process to ensure recommendations are generated only for supported business tables. * **Reference Data Management**: Fixed long description visibility by allowing complete descriptions to be viewed without entering edit mode. * **Data Quality Rules**: Corrected NULL value handling in execution results and replaced generic reference column labels with configured column names, improving result accuracy and report readability. * **Lineage**: Fixed Cognos lineage generation, improved Power BI Auto Lineage processing. * **Connectors (QuickBase)**: Corrected authentication requests to enable successful schema crawling. * **Security**: Enhanced report access by automatically extending permissions to associated sub-reports, and added Service Principal–based authentication support for the Snowflake Connector to align with enterprise authentication standards. * **Advanced Jobs**: Fixed the Sensitive Data Encryption Migration job to ensure that all supported sensitive data, including profiling statistics and minimum/maximum values, is successfully encrypted. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.20release7.2.5.20.725203ec97efJuly 08, 2026
## Data Catalog ### Fixed **Resolved Quickbase Table Profiling Issue** In Data Catalog, an issue where profiling did not run for Quickbase tables when started from the table page has been resolved. The profiling job completed successfully but did not generate profiling results, even when the selected table contained data. Table-level profiling now runs correctly and generates the expected profiling statistics. ## Data Classification Recommendations ### Fixed **Resolved Temporary Table Recommendation Issue** In Data Classification Recommendations, an issue where recommendations were generated for temporary tables has been resolved. Temporary tables were included in the recommendation process, resulting in irrelevant recommendations alongside valid business tables. The recommendation process has been updated to exclude temporary tables, ensuring recommendations are generated only for supported business tables. ## Reference Data Management ### Fixed **Resolved Long Description Visibility Issue** In Reference Data Management, an issue where long descriptions could not be fully viewed without entering edit mode has been resolved. Descriptions were limited to a few visible lines, making it difficult to read complete details. The description field has been updated to allow full viewing of the content without requiring edit mode. ## Data Quality Rules ### Fixed **Resolved NULL Value Display in Data Quality Results** In Data Quality Rules, an issue where execution results displayed NULL values as 0 for certain columns has been resolved. Execution results did not always match the source data, leading to NULL values appearing incorrectly in some cases. The results now accurately preserve and display NULL values, matching the source data. **Resolved Generic Reference Column Labels in DQ Reports** In Data Quality Rules, an issue where failed values reports displayed reference columns with generic labels such as 'ref\_col\_1' and 'ref\_col\_2' instead of the configured column names has been resolved. Failed values reports now display the actual reference column names, making the reports easier to understand and helping identify affected data more accurately. ## Lineage ### Fixed **Resolved Cognos Lineage Generation Failure** In Cognos Lineage, an issue where lineage generation failed because the Bridge Client could not access the required model.xml file has been resolved. The file access process was corrected to ensure the Bridge Client can read the model.xml file from the configured location, enabling lineage generation to complete. **Power BI Auto Lineage Generation Fix** In the Power BI Connector, an issue in which Auto Lineage generation for new or changed source code failed during execution has been resolved. The lineage build process could run for an extended period before failing to complete. The processing logic has been improved to ensure lineage generation completes successfully for new and updated source code. ## Connectors ### Fixed **QuickBase Connector Authentication Fix** In the QuickBase Connector, an issue in which schema crawling failed due to an invalid request sent during authentication has been resolved. The connector now correctly authenticates with QuickBase, allowing schema crawling to complete successfully. ## Security ### New & Improved **Improved Access to Report Sub-Reports** Granting access to a report through the Security module allowed users to view only the parent report. If the report contained sub-reports, users received an Access Denied message because the required permissions were not automatically applied to the sub-reports. With this enhancement, access to a report automatically extends to its associated sub-reports, allowing users to open them and view their related information without requiring separate access configuration. **Service Principal Authentication for the Snowflake Connector** The Snowflake connector now supports Service Principal (OAuth) Authentication in addition to Username & Password and Key Pair Authentication, providing an additional secure authentication option for connector configuration. {% hint style="info" %} Service Principal Authentication does not support the ACCOUNTADMIN, SECURITYADMIN, ORGADMIN, or GLOBALORGADMIN roles. Use a dedicated custom role with the required permissions for successful authentication. {% endhint %} ## Advanced Jobs ### Fixed **Sensitive Data Encryption Migration Fix** In Advanced Jobs, an issue where the "Sensitive Data Encryption Migration" job failed to encrypt all configured sensitive data has been resolved. In some cases, the migration completed with partial success, leaving minimum and maximum values unencrypted. The migration process has been updated to ensure successful completion and to encrypt all supported sensitive data, including top values, minimum and maximum values, and profiling statistics. *** 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.20.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.