# Release7.2.5.5 This release introduces key enhancements and bug fixes across Login, Data Catalog, Query Sheet, Jobs, Load Metadata from Files, Lineage, Connectors, Data Access Management, Job Workflow, and Users & Roles, improving session handling, metadata accuracy, query reliability, lineage precision, connector stability, access synchronization, workflow efficiency, and team management. **Key Highlights** * **Data Catalog**: Corrected schema filter behavior to exclude inactive schemas after regex-based crawls, ensuring only active schemas appear in filters. * **Query Sheet (Salesforce)**: Fixed drag-and-drop query generation to include explicit fields, ensuring Salesforce queries return data as expected. * **Jobs**: Prevented unintended execution of Elasticsearch jobs during crawl or profile actions, ensuring metadata remains visible without interruption. * **Load Metadata from Files (Qlik Sense)**: Fixed the TFIELD column deletion issue to ensure that removed columns are permanently deleted and no longer appear in reports or the data catalog. * **Lineage**: * Improved Informatica PowerCenter lineage accuracy by incorporating session-level configurations. * Corrected lineage mapping in Amazon QuickSight to link dashboards to actual source tables instead of temporary tables. * Fixed SAP BO Universe alias handling to map aliases to underlying warehouse tables for complete lineage. * **Connectors**: * Introduced a new ServiceNow connector to crawl HR database schema metadata using a Scripted REST API and OAuth 2.0 authentication. * Resolved Power BI connector validation failures caused by authentication issues, enabling successful connection validation. * Fixed parse-failed errors in SAP HANA views to ensure consistent parsing across environments. * **Data Access Management (Snowflake)**: Corrected role synchronization and privilege handling, ensuring roles, grants, and permissions are accurately reflected between the application and Snowflake. * **Job Workflow**: Added support for executing multiple workflows in a single action, enabling batch processing and improving operational efficiency. * **Users & Roles (Teams)**: Fixed team management issues that prevented editing, member assignment, or deletion of newly created teams without members. **Release Details**:
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.5Release7.2.5.5.7255923add018th March 2026
## Data Catalog ### Fixed **Inactive Schemas No Longer Shown in Filters** In Data Catalog, an issue where schemas marked as inactive still appeared in schema filters after a regex-based crawl has been resolved. After crawling a connection with selected schemas using regex include rules, some schemas were set to inactive in the Security settings. However, these inactive schemas continued to appear in the schema filters on the Table page, which was unexpected. The filtering logic has been corrected to exclude inactive schemas, ensuring that only active schemas are displayed in Data Catalog filters. ## Query Sheet ### Fixed **Fix for Drag-and-Drop Salesforce Queries Returning No Data** In the Query Sheet, an issue where dragging and dropping a Salesforce object generated a generic query (such as SELECT \*) that returned no data has been resolved. Salesforce does not support generic queries without explicitly defined fields. As a result, queries created through drag-and-drop did not return records, even when data existed. Queries created using the selection option worked correctly because they included specific fields. The query generation logic has been updated to include explicit fields when Salesforce objects are added, ensuring that queries return the expected data regardless of how the object is inserted. ## Jobs ### Fixed **Resolved Unexpected Elasticsearch Job Execution** In Jobs, an issue in which the Elasticsearch job was triggered whenever the Crawl or Profile button was clicked after a connector selection had been resolved. The job started immediately for each action, temporarily preventing metadata from appearing in the Data Catalog until the job finished. The triggering logic has been updated to prevent unnecessary execution of Elasticsearch jobs, ensuring metadata remains visible during crawl and profile operations. ## Load Metadata from Files ### Fixed **Qlik Sense | TFIELD Column Deletion Fix** In Qlik Sense, an issue in which crawled column objects (TFIELDS) deleted via LMDF were reported as successfully removed but remained in the application and appeared in the data catalog has been resolved. Reports returned more TFIELD columns than actually existed in the dashboard. Extra columns marked for deletion were not physically removed, even though the deletion job completed successfully. The deletion process has been corrected to ensure that TFIELD columns marked for removal are permanently deleted and no longer appear in reports or the data catalog. ## Lineage ### Fixed **Informatica PowerCenter | Lineage Accuracy Improvement** In Informatica PowerCenter, an issue in which lineage showed incorrect source mappings has been resolved. Lineage was populated from the mapping, even though the actual session pointed to a file location. The lineage process evaluated mappings only and did not consider session-level details. The lineage logic has been updated to consider both mappings and session configurations, ensuring accurate lineage representation for tables and data sources. **QuickSight Connector | Lineage Mapping Fix** In the Amazon QuickSight Connector, an issue where lineage was created for a temporary lineage table instead of the actual source table has been resolved. Dashboards and analyses were linked to the temporary table, while the real relational source table and dataset were not visible in the lineage view. In addition, the schema for the temporary table could not be identified during lineage correction. The lineage logic has been updated to correctly map datasets to the actual source tables and display the appropriate schema information, ensuring accurate end-to-end lineage. **SAP BO Lineage Fix for Universe Aliases** In SAP BO Reports, an issue where lineage for SAP BO Universe aliases did not connect to the corresponding data warehouse tables has been resolved. Aliases in BO Universes reference actual warehouse tables, but this relationship was not recognized during lineage processing. As a result, lineage stopped at the alias level, causing incomplete traceability for reports that use aliases. The lineage logic has been updated to map Universe correctly, aliases to their underlying warehouse tables, ensuring complete and accurate end-to-end lineage. ## Connectors ### New & Improved **ServiceNow Connector for Crawling HR Database Metadata** A new ServiceNow connector has been introduced to extract HR database schema metadata for integration with the application. Previously, there was no standardized mechanism for crawling HR-related tables in ServiceNow, limiting visibility into HR data assets and their structures. With this implementation, a Scripted REST API in ServiceNow exposes schema metadata for a predefined set of HR tables, enabling the connector to securely retrieve them. The integration uses OAuth 2.0 authentication and a dedicated web service account to ensure controlled, secure access while following enterprise API best practices. This enhancement enables automated discovery of HR database structures from ServiceNow, improving metadata ingestion and supporting governance use cases that require visibility into HR data sources. ### Fixed **Power BI Connector Validation Authentication Fix** In Power BI Connector, an issue where the connector validation failed with an "HTTP 401 Unauthorized" error despite correct connection details has been resolved. The connector could not authenticate during validation, even though the server was reachable, credentials were valid, and required permissions were in place. The authentication process has been corrected to ensure successful validation when valid connection information and credentials are provided. **Fix for Parse-Failed Errors in SAP HANA Views** In SAP HANA Connector, an issue where view parsing failed and produced parse-failed errors for multiple views has been resolved. All views returned parse-failed codes in certain environments, even though most of the same objects parsed successfully elsewhere using identical artifacts. This inconsistency caused many views to fail during processing. The parsing logic has been corrected to ensure consistent handling of SAP HANA views across environments, thereby eliminating parse-failure errors. ## Data Access Management ### Fixed **Corrected Snowflake Role Assignment and Privilege Handling** In Data Access Management | Snowflake (Key Pair Authentication), an issue where roles and privileges were not synchronized correctly between the application and the Snowflake source system has been resolved. Roles already assigned in Snowflake were not reflected in the application, even though other details, such as the default warehouse, were visible. In addition, roles created in the application were marked as successfully created, but were not present in Snowflake. Attempts to grant the 'APPLY\_TAG' privilege also failed with an insufficient permission error despite the service role having 'MANAGE GRANTS' permission. The synchronization logic and privilege handling have been corrected to ensure that role assignments are accurate, newly created roles are properly created in Snowflake, and supported privileges can be granted as expected. ## Job Workflow ### New & Improved **Job Workflow | Execute Multiple Workflows in a Single Action** An enhancement has been implemented in the Job Workflow module to enable multiple Job Workflows to run simultaneously. Previously, when users selected multiple Job Flows on the Job Workflow Information screen, the Execute option was disabled, which limited execution to a single workflow at a time and impacted operational efficiency. With this update, users can now select multiple Job Flow Names and trigger execution in a single action. The Execute option remains enabled for multi-selection, enabling batch processing of workflows without running them individually. This improvement streamlines operations and reduces manual effort when managing multiple workflows. ## Users & Roles ### Fixed **Users & Roles | Team Management Issue Fixed** In Users & Roles | Teams, an issue in which newly created teams could not be edited, members assigned, or deleted has been resolved. Attempts to update the team description, add members, or remove the team displayed a generic technical error message. This issue occurred primarily for teams without any assigned members, while teams with existing members functioned correctly. The team management logic has been corrected to allow editing descriptions, assigning members, and deleting teams regardless of whether members are already assigned. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.