# Release7.2.5.4 This release introduces key enhancements across the Chrome Extension, Connectors, Data Access Management, Service Desk Administration, and System Settings, improving usability, crawl reliability, metadata consistency, authentication handling, and session management. **Key Highlights** * **Chrome Extension**: Improved asset name visibility by displaying object names first, followed by connection and schema details, allowing users to identify assets more easily without relying on hover tooltips. * **Data Catalog**: Enhanced Code Quick View to display code snippets and added a Copy Code option, enabling users to review and reuse lineage-related scripts directly from the interface. * **Load Metadata from Files (LMDF)**: Corrected validation logic for the CDE field in empty LMDF templates, allowing uploads to complete successfully when the field is left blank as intended. * **Connectors (SQL Server)**: Fixed a source job failure caused by service account connections interfering with database state changes during read-only mode transitions. * **Connectors (Power BI)**: * Resolved NullPointerException errors that prevented certain report groups from being crawled. * Fixed report preview loading issues and ensured all permitted workspaces are detected during crawl and profile operations. * **Connectors (Delta Lake)**: * Resolved Java heap space errors during schema crawls by improving memory handling. * Preserved manually updated table titles during schema crawls, preventing them from reverting to physical table names. * **Data Access Management (RDAM – Snowflake)**: Fixed Key Pair authentication configuration handling to ensure successful crawling of Snowflake users and roles. * **Service Desk Administration (ServiceNow Integration)**: Corrected ticket creation failures by ensuring all Best Contact Method options are properly transmitted during ServiceNow ticket creation. * **System Settings**: Fixed session extension behavior so that selecting Continue Session properly refreshes and extends the active session according to the configured timeout. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.4Release7.2.5.4.725470a7beb
9th Mar 2026
## Chrome Extension ### New & Improved **Chrome Plug-in | Display Full Asset Names Without Hover** An enhancement has been implemented in the Chrome Plug-in to improve the visibility of data asset names in the Data tab. Previously, asset names were displayed in the fully qualified format (Connection.Schema.Object). Due to the limited width of the extension panel, long names were truncated with an ellipsis (“...”), requiring users to hover over each asset to view the full name in a tooltip. This issue made it difficult to quickly identify assets, especially when many shared similar connections and schema prefixes. With this update, asset names are now displayed with the object name first, followed by the connection and schema in parentheses — *Object Name (Connection.Schema)*. This format prioritizes the most distinguishable part of the asset within the visible space, allowing users to identify assets more easily, even when names are truncated. The tooltip follows the same format, ensuring consistency and improving usability when searching and selecting assets. ## Data Catalog ### Fixed **Data Catalog | Code Quick View – Display Code Snippet and Copy Code Option** An enhancement has been made to improve the usability of Code Quick View. Previously, the Code Quick View panel did not display the code snippet and did not provide an option to copy the code directly from the interface. This made it difficult for users to review or reuse code when analyzing lineage-related scripts. With this enhancement, the Code Quick View panel now displays the code snippet and includes a Copy Code option. Users can easily view and copy the displayed code from the interface. This improvement simplifies workflows when reviewing lineage-related code, such as Azure Data Factory (ADF) pipelines. ## Load Metadata from Files ### Fixed **Corrected CDE Field Validation in LMDF Template** In LMDF, an issue where uploading an empty LMDF template failed due to incorrect validation of the CDE (Critical Data Element) field has been resolved. The CDE field was not marked as mandatory in the empty template. However, the system still treated it as required and returned a validation error when the field was left blank. This issue prevented the template upload from completing successfully. The validation logic has been corrected to align with the template guidelines. LMDF template uploads now complete successfully when the CDE field is left empty in the empty template. ## Connectors ### Fixed **Resolved Source Job Failure During Database State Change** In SQL Server Source Jobs, an issue was resolved where the source job failed when the database state changed during job execution. Previously, the source job temporarily changed databases from read-only mode to allow updates. After the updates were completed, the job attempted to change the databases back to read-only mode. If another connection accessed the database during this process, the job failed. In some cases, a service account connection occurred while the job was running, preventing the database from switching back to read-only mode and causing the job to fail. The process has been updated to prevent service account connections from interfering with the database state change, ensuring that the source job completes successfully without unexpected connection conflicts. **Resolved NullPointerException During Power BI Report Group Crawl** In Power BI Connector, an issue where crawling certain report groups failed with a null pointer exception has been resolved. During crawl or profile operations, the report groups consistently returned errors and could not be crawled. Logs showed a NullPointerException during the crawling process. The crawling logic has been corrected to handle these scenarios properly, allowing the affected report groups to be crawled successfully without errors. **Delta Lake Connector | Fixed Java Heap Space Error During Crawl** In Delta Lake Connector, an issue where crawling metadata from Delta Lake (Databricks) failed with a java.lang.OutOfMemoryError: Java heap space error has been resolved. The error occurred during schema crawling, even though the JVM heap sizes for UI Service and Job Service were configured to 24GB. The failure appeared during later stages of the crawl, such as relationship processing, even for schemas with a moderate number of tables. Memory handling in the crawling process has been improved to prevent excessive heap consumption. Crawls for Delta Lake (Databricks) schemas now complete successfully without triggering the Java heap space error. **Resolved Report Preview and Workspace Detection Issue in Power BI** In Power BI Connector, an issue in which report previews failed to load for some reports and certain workspaces did not appear during crawl and profile operations has been resolved. Some reports could not be viewed in the Report Preview tab, and several report groups or workspaces were not listed during crawl configuration. This issue occurred even though the required permissions were correctly configured at the Power BI source. The crawling and preview logic has been updated to correctly detect accessible workspaces and reports. Report previews now load properly, and all permitted workspaces appear during crawl and profile operations. **Preservation of Manually Updated Titles in Delta Lake Crawls** In Delta Lake (Service Principal), an issue where manually updated table titles from Data Catalog reverted to the physical table name after a schema crawl has been resolved. Manually entered titles were saved successfully and recorded in the title history. However, after a schema re-crawl, the title was reset to the physical table name. This behavior occurred for both tables and views, even though the schema name and related metadata remained unchanged. The schema crawl process has been corrected to preserve manually defined titles. Titles now remain unchanged after a schema crawl and are no longer overwritten by the physical table name. ## Data Access Management ### Fixed **RDAM | Snowflake Connector – Key Pair Authentication Crawl Fix** In RDAM | Snowflake Connector, an issue where crawling users and roles using Key Pair authentication failed has been resolved. The connector was configured with Key Pair authentication, but the related settings were not reflected at the instance level. Key Pair authentication fields were not visible, and instance-level details could not be edited. As a result, the crawler could not authenticate correctly, and users and roles were not fully retrieved during the crawl. The configuration handling has been corrected so that Key Pair authentication settings are properly recognized at the instance level. Crawling now authenticates successfully and retrieves Snowflake users and roles as expected. ## Service Desk Administration ### Fixed **Resolved ServiceNow Ticket Creation Issue with Contact Method** In ServiceNow Integration, an issue where the Best Contact Method field was not correctly synced when creating service desk tickets has been resolved. When Business Phone or Microsoft Teams was selected in the Best Contact Method dropdown, the value was sent as blank during the integration. As a result, the ServiceNow ticket was not created. The Email option, which is the default selection, worked as expected. The integration logic has been corrected to ensure that all Best Contact Method options are properly captured and transmitted, allowing ServiceNow tickets to be created successfully. ## System Settings ### Fixed **Session Extension Issue Fixed in System Settings** In System Settings, an issue where clicking the Continue Session button on the session expiration notification did not extend the active session has been resolved. After the configured session timeout period (ovaledge.session.timeout), the expiration notification appeared as expected. However, selecting Continue Session did not refresh the session. The session still expired according to the original timeout, and access to certain pages, such as Data Product pages, remained visible even after the session should have ended. The session-handling logic has been corrected so that selecting Continue Session properly extends the session according to the configured timeout. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.