# Release7.2.5.8 This release introduces key enhancements and bug fixes across Login, Data Catalog, Data Quality, Query Sheet, Lineage, Connectors, Users & Roles, and System Settings, improving security controls, search accuracy, data consistency, lineage completeness, connector reliability, and system usability. **Key Highlights** * **Tags**: Fixed the detailed tags template download process to ensure templates are generated successfully, and download links are created correctly. * **Data Catalog**: * Updated Simple Download to use the configured 'download.row\.limit' value, ensuring the UI and exported record count stay aligned. * Fixed search behavior to correctly return objects with empty Business Descriptions. * Corrected metadata upload status to display accurate job results instead of false failures. * Resolved the CDE filter issue to ensure filters remain active after tab navigation. * Removed inactive users from Governance Roles, ensuring only active contributors are displayed. * Corrected Detailed Download behavior so Last Meta Sync Date filters are properly applied during export. * **Query Sheet**: * Corrected pagination logic to display accurate page counts. * Fixed SQL paste formatting issues to preserve query structure and prevent execution errors. * **Lineage**: * Improved Power BI auto lineage accuracy by adding support for additional report structures, ensuring more complete and reliable lineage information. * Fixed Snowflake Auto Lineage parsing to eliminate “Parse Failed” results and incomplete lineage. * Fixed incomplete lineage generation for source code and extracted queries by enhancing parser support. * Corrected lineage mapping in Unity Catalog to ensure accurate object associations. * Resolved lineage job failures in Power BI Bridge to ensure successful execution. * Fixed incomplete and incorrect lineage in Dell Boomi by correcting file names, removing stale data, and improving column mapping. * Addressed parse failures in DB2AS400 views to support complex view processing. * Removed incorrect “Ambiguous column found” warnings that appeared even when the column was not part of the function or query. * Corrected inaccurate Lineage Status messages so users now see error details that match the actual issue encountered during lineage processing. * **Connectors**: * Added a View Password option in the connector configuration. * Added Regex-based subfolder filtering for IBM Cognos crawling to reduce processing time and improve control. * Fixed missing report columns for large Power BI (PBIX) files to ensure complete metadata capture. * Corrected the alias name display in Qlik Sense reports for accurate column representation. * Resolved the incorrect “Partial Success” status in Tableau crawls after successful connection validation. * Fixed incomplete lineage in Qlik Sense dashboards by improving script and intermediate table handling. * Addressed profiling failures for unsupported data types in Delta Lake. * Fixed SQL Server connector login issues to ensure proper authentication and data loading. * Removed mandatory credential requirement for role-based authentication in the Elasticsearch connector. * Resolved partial crawl results in Qlik Sense On-Prem to ensure complete data capture. * Added source system details in QVD asset Business Descriptions for better traceability. * Fixed DB2AS400 crawl performance to handle large volumes without memory errors. * Fixed Cognos folder crawling to correctly include configured report paths. * **Data Access Management**: Fixed pagination counts in Data Access Audit so filtered totals now reflect only matching records. * **Job Workflow**: Fixed dropdown refresh behavior to ensure dependent options reset correctly when switching workflow types. * **System Settings**: Fixed missing table selection in Audit Data Archival, enabling retention configuration for the a\_customfield table. **Release Details**:
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.8Release7.2.5.8.725841101c713th April 2026
## Tags ### Fixed **Resolved Detailed Tags Template Download Failure** In Tags, an issue where the detailed tags template could not be downloaded from the Tags page has been resolved. The download process returned errors in the job logs, preventing the template from being downloaded. The download logic has been fixed to ensure the detailed tags template is generated successfully and the download link is created correctly. ## Data Catalog ### New & Improved **Download Limit Updated Based on System Configuration** In Data Catalog, Simple Download was limited to 10,000 records, even when the 'download.row\.limit' system setting was configured with a higher value. The UI also continued to display a maximum limit of 10,000 records, creating a mismatch between the configured setting and the actual download behavior. With this improvement, Simple Download now uses the value configured in the ‘download.row\.limit’ system setting. The limit displayed in the UI and the number of records downloaded align with the configured value. ### Fixed **Fixed Search for Objects Without Business Description** In Data Catalog | Tables, an issue where searching for objects with an empty business description returned no results has been resolved. The search displayed a blank page instead of listing objects with empty descriptions. The search logic has been updated to correctly identify and display objects without a business description. **Resolved Incorrect Failure Status in Metadata Upload** In Data Catalog | Table Column summary, an issue where metadata upload showed as failed with null errors, even though the data was uploaded, has been resolved. The upload process triggered an error in the job logs, causing the job to appear as failed even though the data was successfully processed. The process has been fixed to ensure correct job status and error handling. **Resolved CDE Filter Inactivity After Tab Switch**\ In Data Catalog, an issue where the Apply Filter button in the CDE filter became disabled after switching tabs in a custom view has been resolved. After applying a CDE filter and navigating to another tab, changing the filter value made the Apply Filter button inactive. This issue prevented the new filter from being applied. The filter behavior has been corrected to keep the Apply Filter button enabled whenever the selection changes, even after switching tabs. **Fix for Inactive Users Appearing in Governance Roles** In Data Catalog, an issue where users with no governance activity or metrics were still displayed under Governance Roles has been resolved. Inactive or non-contributing users continued to appear in roles such as Steward or Custodian, even when no activity was recorded. The logic has been updated to show only users with active governance roles or contributions, and to hide users with zero metrics. **Resolved Last Meta Sync Date Filter Issue in Detailed Download** In Data Catalog, an issue where Detailed Download ignored the Last Meta Sync Date filter has been resolved. Filtered data displayed correctly on the screen, but the Detailed Download exported the full dataset rather than only the filtered records. Simple Download worked as expected. The download process has been updated, so Detailed Download now includes only the data that matches the applied filter. ## Data Quality ### Fixed **Fixed Incorrect Color for Passed Data Quality Status** In Data Quality, an issue where the “Passed” status appeared in red instead of green in the data quality rule summary has been resolved. The status color was displayed incorrectly after running custom data quality rules, leading to confusion when interpreting the results. The display logic has been corrected to ensure the “Passed” status appears in green as expected. ## Query Sheet ### Fixed **Fixed Incorrect Pagination Display in Query Sheet** In the Query Sheet, an issue where the page count was displayed incorrectly after running queries has been resolved. The page count did not match the actual number of result pages, resulting in incorrect pagination. The calculation logic has been corrected to ensure the page count accurately reflects the actual query results. **Resolved SQL Paste Formatting Issue in Query Sheet** In the Query Sheet, an issue where pasted SQL queries were not formatted correctly has been resolved. Queries copied without proper spacing were merged into a single line. This issue caused syntax errors during execution. The formatting logic has been updated to preserve proper spacing and structure, ensuring queries run without errors. ## Lineage ### New & Improved **Power BI Auto Lineage Accuracy Improvement** In Power BI Auto Lineage, an issue where some reports showed incomplete or missing lineage information has been resolved. Certain report structures were not fully supported, which caused missing or incorrect lineage details. The lineage logic has been updated to correctly capture these report patterns and provide more accurate lineage information. ### Fixed **Resolved Parse Failures in Snowflake Auto Lineage** In Snowflake Connector, an issue where Auto Lineage generation marked some queries as “Parse Failed” and created incomplete lineage due to SQL parsing limitations has been resolved. Certain queries were not correctly understood because of unsupported or inconsistent SQL syntax. The parsing logic has been updated to handle these cases more effectively, ensuring more accurate lineage results. **Fix for Partial Lineage Generation in Source Code** In Build Auto Lineage, an issue where lineage was not generated for all source code objects has been resolved. The process completed with errors, and only a small portion of the source code was processed, leaving many objects without lineage. The processing logic has been corrected to handle all source code entries properly, ensuring complete lineage generation without errors. **Fix for Parser Failures with New Syntax Patterns** In Build Lineage from Extracted Queries, an issue where the parser failed to handle new syntax patterns, causing jobs to complete with a partial success status, has been resolved. The parser could not process certain query formats, resulting in incomplete lineage generation. The parser has been enhanced to support the new syntax patterns, ensuring complete and accurate job execution. **Resolved Incorrect Lineage Associations in Unity Catalog** In Unity Catalog Lineage, an issue in which lineage mapping did not link to the correct data objects during the Delta Lake lineage build has been resolved. Lineage generation completed, but some mappings pointed to incorrect objects in the application. The mapping logic has been updated to correctly associate lineage with the appropriate data objects. **Resolved Lineage Job Failures in Power BI Bridge** In Power BI Connector with Bridge, an issue where lineage jobs failed during execution has been resolved. Errors occurred when running scheduled lineage workflows, causing the process to stop and preventing lineage from being generated. The execution logic has been updated to handle these failures, ensuring that lineage jobs run successfully and that lineage is generated as expected. **Resolved Incorrect and Incomplete Lineage in Dell Boomi** In Dell Boomi Connector, an issue with incomplete and incorrect lineage results has been resolved. Process file names were captured incorrectly, old lineage data was not removed after deletion, and column mapping did not show correctly from source to target. The logic has been updated to fix file name extraction, remove outdated data, and display accurate column lineage. **Resolved "Parse Failed" Issue in View Lineage** In the DB2AS400 Connector, an issue in which some views showed a "Parse Failed" status during lineage building has been resolved. Certain complex views could not be processed, even when access permissions were correctly configured. As a result, lineage was not generated for those views. The parsing logic has been improved to handle complex views correctly, ensuring successful lineage generation. **Resolved Incorrect Ambiguous Column Warnings in Lineage Logs** In Lineage, an issue where logs displayed an “Ambiguous column found” warning while building lineage for a function, even though the referenced column was not part of the function code or query, has been resolved. The warning was displayed incorrectly, causing confusion during log review. The lineage logic has been updated to prevent incorrect, ambiguous column warnings from appearing in logs. **Resolved Incorrect Lineage Error Messages** In Lineage, an issue where the Lineage Status section displayed incorrect or unrelated error messages has been resolved. The status message did not match the actual issue found during lineage processing, making troubleshooting difficult. The error-handling logic has been updated to display accurate messages that accurately reflect the actual lineage issue. ## Connectors ### New & Improved **View Password Option in Connector configuration** An enhancement has been introduced in connector configurations to improve password verification. With this update, a View Password option is available, allowing users to temporarily reveal and verify the password during configuration, reducing input errors and improving usability. **Regex-Based Subfolder Filtering for Cognos Crawling** An enhancement has been introduced to the IBM Cognos Analytics connector to support Regex-based filtering at the subfolder level during crawling. Previously, crawling was limited to the root folder, and all underlying folders and reports were included by default, resulting in long processing times and large data volumes. With this update, users can define regular expression (Regex) patterns in the connector configuration to include or exclude specific subfolders within the Cognos hierarchy. This update allows only relevant report paths to be crawled, rather than processing the entire structure. As a result, crawling time is significantly reduced, system load is minimized, and administrators can more easily manage and restrict report access in line with business requirements. ### Fixed **Resolved Missing Report Columns for Large PBIX Files** In Power BI Connector, an issue in which report columns did not appear in the Data Catalog after crawling and lineage building for reports with large PBIX files has been resolved. Columns were still missing even after successful crawling, lineage generation, and manual upload of the PBIX file. This issue occurred with reports whose PBIX files exceeded 1.5 GB. The processing logic has been updated to handle large PBIX files correctly, ensuring all report columns are captured and displayed. **Resolved Alias Name Display Issue in Qlik Sense Reports** In Qlik Sense Connection, an issue where report columns with alias names were not displayed correctly has been resolved. Columns defined with an alias were shown with the original name instead of the alias—for example, CITY\_CD\_ASSIGN as %CITY\_ID% did not display as %CITY\_ID%. The logic has been updated to correctly display column names based on the defined alias. **Resolved Incorrect “Partial Success” in Tableau Crawls** In Tableau Connector, an issue where crawl jobs showed a “Partial Success” status after successful connection validation has been resolved. The connection initially failed due to an SSL handshake error, which was fixed by updating and importing the required SSL certificate. However, crawl jobs were still completed with partial results even though the connection was valid and permissions were correct. The crawl handling has been corrected to ensure jobs complete successfully and return full results after a valid connection is established. **Resolved Incomplete Lineage in Qlik Sense Dashboards** In Qlik Sense, an issue where dashboard lineage did not correctly connect to source systems in certain scenarios has been resolved. Lineage gaps occurred due to incomplete script processing, missing QVD references, and incorrect mapping of intermediate tables (resident or temporary). As a result, some dashboard objects could not be traced back to the source data warehouse or external files. The lineage logic has been updated to correctly link intermediate tables, handle QVD and file-based sources, and ensure complete end-to-end lineage from dashboards to source systems. **Resolved Profiling Errors for Unsupported Data Types in Delta Lake** In Delta Lake Connection, an issue where the profiling job failed with a “Not Supported” or data type mismatch error for certain table columns has been resolved. The job encountered errors due to unsupported complex data types, such as map\>, which caused SQL processing failures. This issue has been fixed to handle such data types correctly, ensuring that profiling jobs execute successfully. **Resolved Login Failure in SQL Server Connector** In SQL Server Connector, an issue where the Data tab remained stuck after entering valid database credentials has been resolved. The login process failed after credentials were submitted, and data was not loaded despite having the correct permissions. The login flow has been fixed to ensure successful authentication and proper data loading in the Data tab. **Resolved Mandatory Credential Issue in Role-Based Authentication** In the Elasticsearch Connector, an issue where a username and password were required even for role-based authentication has been resolved. These fields were incorrectly marked as mandatory. The connector now makes username and password optional when role-based authentication is selected. **Resolved Partial Crawl Results in Qlik Sense**\ In Qlik Sense On-Prem, an issue where report groups that were completed with a “Partial Success” status were not being crawled has been resolved. The crawl process did not complete fully, even after applying the recommended database changes. As a result, some report group data was not captured. The crawling process has been updated to complete successfully and to ensure that all report group data is captured, without partial results. **Resolved Missing Source Information in QVD Assets**\ In QVD Generator, an issue where generated assets did not include source system details in the Business Description has been resolved. The Business Description field did not indicate the asset's origin, making it difficult to identify its source. The generation process has been updated to automatically include source information in the Business Description, improving visibility into the asset's origin. **Resolved Memory Error in Large Table Crawls** In the DB2AS400 Connector, an issue in which crawling a large number of tables failed with a partial success status has been resolved. The crawl process stopped due to a memory error while processing a source containing approximately 52,000 tables. This issue caused incomplete results after a long execution time. The crawling process has been improved to efficiently handle large volumes of tables, preventing memory errors and ensuring complete results. **Resolved Missing Reports in Cognos Folder Crawling** In Cognos Connector, an issue where the 'cognos.onprem.includefolders' setting did not include reports from specified folders during crawling has been resolved. Configured folder paths were accepted, but reports in those folders were neither ingested nor displayed. This issue occurred even after increasing the parameter size limit. The processing logic has been updated to read the configured folder paths correctly and include all reports from those folders during crawling. ## Data Access Management ### Fixed **Corrected Filtered Record Count in Data Access Audit** In Data Access Audit, an issue in which the pagination count in the Users tab displayed incorrect totals after applying action filters has been resolved. When filters such as Delete or Edit were selected, the page displayed only the matching records, but the pagination count included records from all actions. The pagination logic has been updated so the total count now reflects only the records that match the selected filters. ## Job Workflow ### Fixed **Resolved Dropdown Refresh Issue in Job Workflow** In Job Workflow, an issue where the “Select Type” dropdown did not reset when switching between options has been resolved. After selecting one type, such as Profile, related options remained visible even after changing to another type, such as Anomaly. This issue caused confusion as outdated options continued to appear. The dropdown behavior has been corrected to clear and refresh dependent options whenever a new type is selected. ## System Settings ### Fixed **Resolved Table Selection Issue in Audit Data Archival** In System Settings | Audit Data Archival, an issue where the a\_customfield table was not available in the table selection dropdown has been resolved. This issue prevented adding a retention period to the a\_customfield table. The dropdown list has been updated to include the a\_customfield table, allowing retention settings to be configured. ## Known Issues **Data Catalog (Databases)**: Downloading the Detailed Metadata Template returns an empty file when multiple filters or search criteria are applied. Although the UI displays the correct filtered records, the export does not reflect these filters, resulting in a mismatch between the UI and downloaded data. **Business Glossary**: All glossary terms are downloaded when using the detailed download template, even if a download limit is configured in system settings. The configured limit is not applied, resulting in the export of all available terms instead of the expected restricted set. **LMDF Download / Data Quality Access**: Non-OE\_ADMIN users (e.g., the MWDW role) can download Data Quality rules via the LMDF template, even without UI access to the Data Quality module. The download process does not enforce RBAC (Role-Based Access Control) restrictions, exposing restricted data during export. **LMDF / Column Relationships**: The “Download Template (with data)” option ignores user permissions and exports all column relationship data. Users with restricted access (e.g., MWDW role) can download data from unpermitted domains and assets. Role-based access control (RBAC) is not enforced during export, leading to unauthorized data exposure. **Users & Roles**: Detailed Download fails after applying filters, resulting in a ‘BadSqlGrammarException’ during job execution. The SQL query incorrectly applies filters in the HAVING clause instead of the WHERE clause, causing the job to fail and no download file to be generated. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions: 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: ``` GET https://docs.ovaledge.com/hotfix-releases/release7.2.5.x/release7.2.5.8.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.