Release7.2.4.1
This release introduces key fixes across Login, Tags, Data Catalog, Business Glossary, Question Wall, Data Access Management, Connectors, Lineage, Service Desk, and System Settings, improving stability, accuracy, and overall platform reliability.
Key Highlights
Login Stability: Resolved an issue that triggered repeated authentication prompts during re-login.
Tag Accuracy: Resolved incorrectly tagged objects and page size inconsistencies in list views.
Catalog Improvements: Resolved duplicate fields, subreport visibility issues, and missing columns in tree views.
Report Accessibility: Resolved an issue that restricted access to parent reports.
Glossary Accuracy: Resolved count inconsistencies between summaries and associated objects.
Question Wall: Resolved an issue that prevented the reply option from appearing during edits.
Access Validation: Resolved an instance validation error caused by firewall restrictions.
Curation Retention: Resolved an issue that removed curated descriptions during Power BI crawls.
Lineage Display: Resolved missing lineage for specific objects during extraction.
Service Desk: Resolved missing classification values during request creation.
Archival Defaults: Resolved issues with default retention settings not aligning with table categories.
Release Details:
Hotfix Release
Release7.2.4.1
Release7.2.4.1.7241389f997
9th Dec 2025
Login
Fixed
Application Login | Repeated Microsoft Authentication Prompt
In the Application Login process, an issue occurred where a repeated authentication prompt appeared after logging out and logging in again. The issue has been resolved by updating the session handling logic, and the login process now functions without repeated prompts.
Tags
Fixed
Tagged Report Columns Not Displayed
In the Tags module, an issue occurred where tagged report columns were not visible, and an error appeared while accessing the tag. The issue has been resolved, and tagged columns now display correctly.
Page Size Not Retained in Custom View
In the Tags module, an issue occurred where selected page size values were not retained in custom views and reverted to the default. The issue has been resolved through configuration updates, and custom views now retain the selected page size.
Data Catalog
Fixed
Duplicate Column Position Fields
In the Data Catalog module, the table column list view displayed the column position twice. This occurred after opening the table column summary page, creating a view for the table columns, and searching for column position. The issue has been resolved by removing the extra field, and the column list now displays the correct structure.
Subreport Tab Visibility Issue
In the Data Catalog module, an issue occurred where the subreport tab appeared inconsistently while navigating through reports and report columns. The issue has been resolved by aligning the configuration, and the subreport tab now behaves consistently.
Sub Reports | Columns Missing in Tree View
In the Data Catalog module - Report Column Summary Page, an issue occurred where columns were not displayed in the tree structure, while the list view displayed them correctly. The issue has been resolved by updating the query, and columns now appear correctly in the tree view.
Reports | Parent Report Not Accessible
In the Data Catalog module, an issue occurred where accessing a parent report displayed an unavailable message while child reports remained accessible. The issue has been resolved by updating the access logic, and parent reports now open as expected.
Business Glossary
Fixed
Count Mismatch in Summary and Associations
In the Business Glossary module, an issue occurred where summary counts and associated object counts did not match. The issue occurred because inactive objects were reflected in the summary. The issue has been resolved with updated processing logic, and counts now align as expected.
Question Wall
Fixed
Question Wall | Reply Button Not Displayed During Edit
In the Question Wall module, an issue occurred where the reply option was not displayed while editing a response, and the interface displayed the ask action instead. The issue occurred because the reply configuration was not passed to the required component during rendering. The issue has been resolved by updating the component configuration, and the correct reply option now appears during edits.
Data Access Management
Fixed
Data Access Management | Instance Validation Error
In the Data Access Management module, an issue occurred where the instance validation failed with an access error. The issue occurred because the IP address used for validation was not permitted by the database firewall, and the validation process required updates to handle this condition without dependency on IP whitelisting. The issue has been resolved through the required code fix and configuration update, and the instance validation now functions as expected.
Connectors
Fixed
Power BI | Curated Business Description Not Retained
In the Power BI connectors, an issue occurred where curated descriptions added to reports were removed after scheduled crawling. The issue occurred because object identifiers changed during republishing, causing previously curated information to become inactive. The issue has been resolved by introducing a stable identification approach, and curated descriptions now remain intact after crawling activities.
Lineage
Fixed
Lineage Not Displayed for Specific Object
In the IBM InfoSphere DataStage connectors, an issue occurred where lineage did not appear for a specific object while other objects displayed lineage correctly. The issue occurred because the lineage information for that object was not processed during extraction. The issue has been resolved by updating the extraction logic, and lineage now appears as expected.
Service Desk
Fixed
Service Desk | Classification Values Not Displayed
In the Service Desk module, an issue occurred where classification values were not visible while creating a metadata change request for terms. The issue occurred because the domain reference used by the classification service retrieved an incorrect value. The issue has been resolved by updating the classification logic, and the correct values now appear during request creation.
System Settings
Fixed
Audit Data Archival | Default Settings Not Applied
In the Audit Data Archival module, an issue occurred where default retention values were not aligned with the intended table type categories. The issue occurred because default values were not preconfigured for each category. The issue has been resolved by applying the required defaults in the supported versions, and the retention settings now reflect the correct values with full configurability.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?

