Release6.3.5

Hotfix Release6.3.5.2

This release introduces key enhancements across Data Catalog, Load Metadata from Files, and Connectors, improving data export accuracy, metadata uploads, and cloud integration capabilities.

Key Highlights

Data Catalog: Eliminated duplicate records in view-based downloads by fixing logic for views without ORDER BY clauses.

Data Catalog: Resolved missing columns, incorrect Arabic text rendering, and incomplete row downloads in Table Columns Grid view exports.

Load Metadata from Files: Fixed metadata upload failures and null entries in job logs for Table Column templates, ensuring successful imports.

Connectors (Dell Boomi): Corrected lineage issues by fixing missing components, improper mappings, and preventing cyclic lineage loops in patient extraction workflows.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.2

Release6.3.5.2.63520af3515

5th Dec 2025

Data Catalog

Fixed

Duplicate Records Eliminated in View-Based Downloads

In Data Catalog, an issue occurred when users downloaded data from configured views; the file sometimes contained duplicate rows. This issue happened because the system did not sort the data correctly before exporting. The issue has now been fixed, and the downloaded data is accurate and complete.

Improved LMDF Download Accuracy in Table Columns

In Data Catalog | Table Columns Grid View, an issue occurred when downloading data from a configured view. The downloaded file did not include the expected information as follows:

Columns for Classification and Data Quality Score were missing from the downloaded file.
Arabic text appeared as question marks in the downloaded sheet.
After switching the interface to English, column headers in the downloaded file also appeared as question marks.
Only the first five rows were downloaded in both Arabic and English modes.
Data downloaded in Arabic mode displayed content in English instead of Arabic.

These issues have been resolved, and LMDF downloads now include complete row counts, accurate classification values, and proper Arabic text rendering.

Load Metadata from Files

Fixed

Improved Table Columns Metadata Upload Process

In Load Metadata from Files, an issue occurred where metadata uploads from the Table Column template resulted in Null and Failed entries in job logs has been resolved. The upload process has been corrected to allow successful metadata import through the Load Metadata from Files option.

Connectors

Fixed

Improved Dell Boomi Connector Lineage Accuracy and Loop Prevention

In the Dell Boomi connector, an issue was reported where some components, such as decision branch properties, were missing from the patient extraction process. Additionally, the variable was incorrectly mapped to multiple components. A cyclic lineage (infinite loop) occurred in the DXPX process due to a reference to the source file, leading to an endless cycle.

The lineage validation and build process for the Dell Boomi connector has been corrected to address missing components, fix incorrect mappings, and prevent cyclic lineage loops.

Hotfix Release6.3.5.3

This release introduces key enhancements across Business Glossary, Data Quality, Lineage, Advanced Tools, and Connectors, improving stability, notification clarity, lineage accuracy, parsing reliability, and connectivity support.

Key Highlights

Business Glossary: Fixed domain deletion failures caused by null pointer exceptions, enabling error-free domain removals.
Data Quality: Corrected Rule Purpose rendering in notifications by fixing raw HTML display issues in email and application alerts for custom SQL rules.

Lineage:

- Fixed incomplete lineage extraction for Dell Boomi stored procedures and improved handling of joined tables for accurate lineage display.
- Resolved incorrect upstream lineage mappings in Qlik Sense dashboards by removing unrelated table links for precise fact-dimension relationships.
- Improved lineage mapping in Qlik Sense Connector by recognizing alias names correctly, preventing temporary objects and ensuring accurate upstream lineage.

Advanced Tools - Build Auto Lineage:

- Enhanced Snowflake auto lineage parsing to reduce temporary lineage and parse failures by improving SQL keyword handling.
- Improved SAP HANA view parsing reliability by addressing environment-specific differences, reducing unexpected parse failures.

Connectors:

- Added support for Microsoft Fabric Warehouse connectivity via SQL Server Connector, enabling metadata extraction and Data Quality Rule execution on Fabric Warehouse objects.
- Fixed column alias capture in Qlik Sense reports to accurately store alias names and improve metadata validation and lineage construction.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.3

Business Glossary

Fixed

Domain Deletion Completes Without Errors

In Security | Domains, an issue that caused a null pointer exception when deleting a domain has been resolved. The deletion process failed instead of completing successfully. This issue was fixed by correcting the domain-deletion logic, which now allows domains to be deleted without errors.

Data Quality

Fixed

Correct Rule Purpose Rendering in Data Quality Notifications

In Data Quality Notifications, an issue in which the Rule Purpose text appeared as raw HTML instead of plain text in email and application notifications has been fixed. This issue occurred with custom SQL rules when Rule Purpose content was manually entered or copied, causing readability issues. The notification rendering logic was updated to display the Rule Purpose content correctly as plain text across all notifications.

Lineage

Fixed

Complete Lineage Extraction for Dell Boomi Stored Procedures

In Dell Boomi | Lineage, an issue was identified in which stored procedures were not extracted for a single connector action component. In addition, Lineage displayed only one table when a query joined two tables. The lineage extraction logic was updated to use stored procedures and to display all tables involved in joined queries correctly.

Upstream Lineage Corrected for Qlik Sense Dashboards

In Qlik Sense Lineage, an issue in which the upstream lineage for Qlik Sense dashboards showed incorrect table mappings has been resolved. Unrelated tables were incorrectly linked in the upstream lineage, leading to inaccurate relationships between fact and dimension tables. The lineage logic was corrected to ensure only valid and relevant table relationships are displayed. This fix improves the accuracy of upstream lineage by removing incorrect and unrelated mappings.

Accurate Lineage Mapping for Qlik Sense Dimensions and Measures

In the Qlik Sense Connector, an issue that prevented lineage from being generated correctly for some Dimensions and Measures in reports has been fixed. The problem occurred because the alias names used in formulas did not match the actual source column names. This issue caused the system to create temporary upstream objects instead of linking to the correct data sources, resulting in incomplete or incorrect lineage mapping. The fix improves the lineage logic to recognize and map alias names to their original source columns. This fix ensures accurate upstream lineage without creating temporary objects.

Advanced Tools - Build Auto Lineage

Fixed

Improved Snowflake Auto Lineage Parsing Accuracy

In Build Auto Lineage for Snowflake Connector, an issue was identified in which auto lineage generation produced temporary lineage for several queries and marked a few queries as parse failures. The failures were caused by parsing anomalies related to specific SQL keywords and syntax. The lineage parsing logic was reviewed and improved to better handle Snowflake-specific SQL patterns. Queries with correctable syntax were successfully parsed, and overall lineage-generation accuracy improved.

Improved SAP HANA View Parse Reliability

In SAP HANA Connector, an issue was reported in which view definitions were marked as parse-failed during metadata processing. Approximately 300 views failed to parse on the client environment, even though most of the same artifacts parsed successfully in other environments.

The parsing logic was reviewed and validated to handle environment-specific differences and improve consistency. This update reduces unexpected parse failures and improves the reliability of view parsing and lineage validation.

Connectors

New & Improved

Enabled Microsoft Fabric Warehouse Connectivity via SQL Server Connector

In Connectors, support has been added to connect to Microsoft Fabric Warehouses using the SQL Server connector through the SQL Analytics Endpoint. Previously, customers migrating from SQL Server to Microsoft Fabric could not directly extract metadata or run Data Quality Rules against Fabric Warehouses. This enhancement allows successful connection using the Fabric warehouse endpoint, enables metadata extraction, and supports execution of SQL-based Data Quality Rules on Fabric Warehouse objects.

Accurate Capture of Column Aliases in Qlik Sense Reports

In Qlik Sense Connection, an issue where report columns defined with AS alias syntax were not captured correctly has been resolved. Column aliases, such as CITY_CD_ASSIGN AS %CITY_ID%, are now stored using the alias name as the column name. The fix also ensures accurate metadata validation and correct lineage construction.

Hotfix Release6.3.5.4

This release introduces fixes in the Data Catalog, Lineage, Chrome Extension, Connectors, Data Quality, and Advanced Jobs modules. It improves system performance, stability, and user experience by addressing delays, data inconsistencies, display issues, and reporting gaps.

Key Highlights

Data Catalog – Column Term Removal Issue: Fixed delays in removing term associations from columns.
Lineage – Duplicate Data Flows in Package Associations: Fixed duplicate entries in package associations.
Chrome Extension – Missing Certification Indicator for Reports: Fixed the issue where the certification indicator did not appear on certified reports.
Connectors – Qlik Sense and Power BI Issues: Fixed inconsistent crawling in Qlik Sense and authorization failures in Power BI.
Advanced Job – Reporting for Qlik Sense Crawling Details: Enhanced reporting to capture detailed crawling information and separate crawling and lineage outputs.
Data Quality: Resolved issue related to text display for the Rule Purpose field in notifications.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.4

Release6.3.5.4.63540219ec1

18th Dec 2025

Data Catalog

Fixed

Column Term Removal Issue

In the Data Catalog, an issue occurred where the removal of term associations from columns exceeded the expected processing time. The issue has been resolved by improving the term handling logic, and now term associations are removed within the expected time.

Lineage

Fixed

Duplicate Data Flows in Package Associations

In the Lineage module, an issue occurred where duplicate data flow entries appeared in package associations after a rebuild for the SSIS connector. The issue occurred because existing records were not updated correctly, and older entries were retained during the rebuild process. The issue has been resolved by ensuring existing records are properly refreshed, and now associations display only the correct and current data flows.

Chrome Extension

Fixed

Missing Certification Indicator for Reports

In the Chrome Extension, an issue occurred where the certification indicator was not displayed on certified reports when viewed in the reporting platform. The issue has been resolved by improving certification status handling, and now the certification indicator appears as expected on certified reports.

Connector

Fixed

Qlik Sense | Inconsistent Crawling Across Streams

In the Qlik Sense (On-prem) Connector, an issue occurred where scheduled crawling did not complete consistently across multiple data streams and prevented related processes from proceeding. The issue has been resolved through enhancements to the crawling process, and now crawling runs complete successfully with stable downstream processing.

Power BI | Authorization Failure During Connector Validation

In the Power BI Connector, an issue occurred where connector validation failed with an authorization error even when valid credentials and access were provided. The issue has been resolved through improvements in validation handling, and now connector validation completes successfully in supported environments.

Advanced Job

Fixed

Improved Reporting for Qlik Sense Crawling Details

In the Advanced Job module, an issue occurred where the reporting for Qlik Sense crawling activity did not include complete crawling details. The issue has been resolved by enhancing the job logic to capture detailed crawling information. The crawling and lineage outputs have been separated, and now the report provides clear and complete visibility into Qlik Sense crawling results.

Data Quality

Fixed

Data Quality Notifications – Rule Purpose Display Issue

In the Data Quality Notifications module, an issue occurred where the Rule Purpose field showed HTML code instead of text in both emails and the application. The issue has been resolved, and the Rule Purpose now displays correctly in text format, ensuring notifications are readable.

Hotfix Release6.3.5.5

This release introduces key enhancements across Business Glossary, Lineage, and Connectors, improving term management reliability, lineage accuracy, and large-scale connector performance.

Key Highlights

Business Glossary:

- Fixed an issue where deleting glossary terms associated with schemas failed, ensuring successful term removal without errors.
- Resolved domain deletion failures caused by null pointer exceptions, allowing domains to be deleted reliably.
- Corrected inconsistent bulk tag removal from glossary terms, ensuring all selected tags are removed and jobs complete successfully.

Lineage:
- Fixed incorrect lineage generation in ADF Lineage by correcting code parsing logic, resulting in complete and accurate lineage details.

Connectors:

- Added support for Microsoft Fabric Warehouse connectivity via the SQL Server connector, enabling metadata extraction and SQL-based Data Quality Rule execution on Fabric Warehouse objects.
- Improved DB2 AS400 table crawling reliability by optimizing memory handling, preventing heap space errors, and ensuring successful crawling of large schemas.
- Fixed Qlik Sense app crawling failures caused by inconsistent virtual proxy validation across nodes, enabling standardized proxy handling and consistent crawling in multi-node environments.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.5

Release6.3.5.5.6355e81a4fo

24th Dec 2025

Business Glossary

Fixed

Business Glossary Term Deletion Issue Resolved

In Business Glossary, an issue where deleting a business term failed after it was associated with a schema has been resolved. An unexpected error occurred during the deletion process when a term had an existing schema association. The deletion logic was updated to handle schema-linked terms, allowing for successful removal without errors.

Domain Deletion Completes Without Errors

Consistent Bulk Tag Removal for Glossary Terms

In Business Glossary, an issue where the bulk removal of tags from terms resulted in partial job success has been resolved. The logic for bulk updates has been adjusted to ensure tags are consistently removed from all selected terms, allowing jobs to complete successfully.

Connectors

New & Improved

Enabled Microsoft Fabric Warehouse Connectivity via SQL Server Connector

In Connectors, support has been added to connect to Microsoft Fabric Warehouses using the SQL Server connector through the SQL Analytics Endpoint. Previously, customers migrating from SQL Server to Microsoft Fabric could not directly extract metadata or run Data Quality Rules against Fabric Warehouses. This enhancement enables successful connection to the Fabric warehouse endpoint, supports metadata extraction, and allows execution of SQL-based Data Quality Rules on Fabric Warehouse objects.

Enhanced DB2 AS400 Table Crawling Reliability

In DB2 Connector, an issue where crawling significant DB2 AS400 sources completed with a partial success status has been resolved. The crawl failed due to insufficient memory when processing a very high number of tables, causing the job to stop with a Java heap space error. The crawl process was optimized to handle large schemas better, preventing memory exhaustion and enabling successful table crawling.

Resolved Virtual Proxy Validation Issue in Qlik App Crawling

In the Qlik Sense Connector, an issue has been identified where apps hosted on specific nodes fail to crawl when virtual proxy validation is enabled. The crawling process returned an “app not found” error for one node in a multi-node setup, even though other nodes completed successfully using node-specific virtual proxy prefixes. This issue was addressed by validating and standardizing the handling of the virtual proxy prefix across nodes in the crawling logic. Once the remaining node’s proxy mapping is confirmed, the updated logic will enable consistent app crawling across all nodes in the Qlik environment.

Hotfix Release6.3.5.6

This release introduces usability improvements in User Management and reliability fixes across Connectors, enhancing team visibility, lineage accuracy, and connector stability.

Key Highlights

User Management:
- Enabled direct access to team member details from reference links without requiring additional permissions.

Connectors:
- Improved lineage accuracy for Azure Data Factory and SAP BO connectors.
- Fixed Power BI validation, report preview, and workspace visibility issues.
- Resolved multilingual display issues in SQL Server source descriptions.
- Ensured consistent app metadata crawling across multi-node Qlik Sense environments.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.6

Release6.3.5.6.6356ff0ac84

02nd Jan 2026

User Management

New & Improved

Team Member Visibility Through Reference Links

A new enhancement simplifies how users access team details when a team is referenced in business or technical descriptions. Previously, clicking a team reference redirected users to the Teams module, which restricted visibility for many users, especially those with Viewer licenses who lacked permission to open the Teams page.

With the update, selecting a team reference now opens a shutter displaying the team’s name, description, a searchable list of all members with email addresses, the total number of members, and an option to copy all visible email IDs. This improvement enables users to view essential team information directly from their current page, without navigating away or requiring elevated permissions.

Connectors

Fixed

Enhanced Lineage for ADF Pipelines

In the Azure Data Factory (ADF) connector, an issue occurred where lineage for some pipelines and dataflows was missing or only partially generated. In a few cases, pipelines appeared successful despite incomplete lineage. This issue has been fixed. Lineage for ADF pipelines is now generated correctly, and the system clearly indicates when lineage cannot be built.

Connector Validation Failing with 401 Unauthorized Error

For the Power BI on-premises connector, an issue occurred where validation failed with an HTTP 401 Unauthorized error, even when the correct connection details, username, and password were provided. This caused the connector to fail during validation in environments using Basic authentication. This issue has been fixed. The connector now validates successfully when correct credentials are provided, ensuring reliable authentication for environments that do not use Windows authentication.

Lineage Gap for SAP BO Universe Aliases

For SAP Business Objects (BO) Universes, an issue occurred where lineage was not built correctly when reports used table aliases. Lineage stopped at the alias level and did not connect to the actual data warehouse tables, resulting in incomplete lineage for affected reports. This issue has been fixed. Lineage now correctly resolves aliases and connects them to their corresponding data warehouse tables.

Source Descriptions Not Displaying Arabic Characters Correctly

For the SQL Server connector, an issue occurred where source descriptions written in Arabic were not displayed correctly after crawling. Instead of showing the actual Arabic text, the application displayed “??” in the source description field. This issue has been fixed. Source descriptions containing Arabic and other non-English characters now display correctly in the application. This improvement ensures accurate representation of multilingual metadata and supports better usability for international users.

Report Preview and Workspace Visibility Issues

For the Power BI connector, an issue occurred where some reports could not be previewed, and certain report groups or new workspaces were not visible for crawling or profiling. This happened even though the required permissions were set correctly in the Power BI source. This issue has been fixed. Reports and workspaces are now correctly available for preview and crawling, including scenarios where the report’s dataset is located in a different workspace.

App Metadata Export Issues in Multi-Node Environments

For the Qlik Sense connector, an issue occurred in multi-node environments where app metadata export succeeded for some nodes but failed for others with an “app not found” error when virtual proxy prefixes were used. This issue has been fixed. The connector now correctly handles virtual proxy prefixes and redirection, enabling the successful export of app metadata from all nodes. This improvement ensures consistent crawling across multi-node Qlik Sense environments.

Hotfix Release6.3.5.7

This release introduces key enhancements across Data Catalog, Data Quality, Lineage, Load Metadata from Files, and Job Workflow, improving metadata accuracy, integration efficiency, lineage reliability, manual metadata management, and workflow visibility.

Key Highlights

Data Catalog: Fixed incorrect table column and report counts that appeared after application upgrades. Metadata counts now display accurately, and reports load without errors in the Data Catalog view.
Data Quality: Added delta load support to the DQ Bulk API using the updateDate parameter, enabling efficient incremental retrieval of Data Quality rules and improving integration performance.
Lineage: Corrected column-level lineage for Qlik Sense reports by resolving alias names to their original source columns, ensuring accurate upstream lineage and preventing temporary object creation.
Load Metadata from Files: Introduced an LMDF-based approach for managing manual Qlik Sense report column updates, allowing column definitions to be maintained directly in the LMDF template with clear tracking of column origin.
Job Workflow: Fixed workflow rendering issues that caused blank displays for certain job flows, ensuring consistent and reliable display of workflow details regardless of the number of scheduled Data Quality rules.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.7

Release6.3.5.7.635742c01a0

12th Jan 2026

Data Catalog

Fixed

Data Catalog | Incorrect Table and Report Counts Fixed

In Data Catalog, an issue caused the report and table column counts to be displayed incorrectly after an application upgrade.

The Data Catalog summary showed a table column count of 0, even when columns were present. Reports listed under Data Catalog triggered a generic error message instead of displaying counts. These issues caused a mismatch between the Data Catalog overview and the actual metadata available within the application.

This issue has been resolved by correcting the query logic used to calculate object counts and load report metadata. Table column and report counts now display accurately, and reports load without errors in the Data Catalog view.

Data Quality

New & Improved

Delta Load Support for DQ Bulk API Using Update Date Parameter

An enhancement has been added to the DQ Bulk API (/api/dataquality/getDQRules) to support delta loads using an updateDate timestamp parameter. Previously, the API returned all Data Quality Rules on every request, resulting in unnecessary processing of unchanged data.

With this update, users can pass the updateDate parameter to retrieve only rules that were created or modified on or after the specified timestamp (UpdateDate >= updateDate). If the parameter is not provided, the API continues to return the complete dataset. This improvement enables efficient incremental data loads, reduces payload size, and improves integration performance.

Lineage

Fixed

Corrected Column Lineage for Qlik Sense Reports

In the Qlik Sense Connector, an issue has been identified in which report column lineage was not correctly built for some Dimensions and Measures. Measures and Dimensions in Qlik Sense reports were not linking to their correct upstream data sources. Instead, the system created temporary upstream objects, resulting in incomplete and inaccurate lineage. This occurred because lineage generation relied on column names used in formulas. These formulas referenced column aliases rather than the actual source column names, preventing correct matching with upstream fields.

The lineage logic has been enhanced to resolve alias names to their original source columns by parsing the underlying tables. This update ensures accurate upstream lineage and prevents the creation of temporary objects.

Load Metadata from Files

New & Improved

LMDF-Based Approach for Manual Qlik Sense Column Updates

An enhancement has been introduced to manage manual creation and modification of Qlik Sense report columns by updating the existing LMDF template, rather than implementing a new Advanced Job. Previously, handling manual column changes required additional processing logic, increasing complexity and maintenance overhead.

With this approach, column definitions are maintained directly in the LMDF template, ensuring consistency with the existing ingestion framework. In addition, a new metadata field will be introduced at the report column level to indicate whether a column was created manually, automatically through crawling, or initially created manually and later updated via crawling. This enables clear identification and tracking of column origin and lifecycle, while allowing manual and automated column management to coexist seamlessly.

Job Workflow

Fixed

Improved Job Workflow Display Consistency

In Job Workflow, an issue preventing the display of workflow details for specific job flows has been resolved.

Some Job Flows showed blank content when opened, while others displayed correctly. No error messages were shown. This behavior occurred primarily in workflows that contained multiple Data Quality rules scheduled simultaneously. Historical executions of these rules also contributed to the issue.

The workflow rendering logic has been corrected to ensure all Job Flows display their details consistently, regardless of the number of scheduled Data Quality rules.

Hotfix Release6.3.5.8

This release introduces key fixes across Business Glossary, Impact Analysis, Build Auto Lineage, and Data Access Management, improving data visibility, download reliability, parsing consistency, and Snowflake access configuration.

Key Highlights

Business Glossary: Fixed a pagination issue that displayed zero records despite existing entries, restoring correct record counts and re-enabling the download option.
Impact Analysis: Resolved download failures for Impacted Objects after job completion by fixing file retrieval errors and standardizing downloads to XLSX format.
Build Auto Lineage (SAP HANA): Improved view parsing reliability by correcting parse-handling logic, ensuring consistent parsing results across environments using the same artifacts.
Data Access Management (Snowflake RDAM): Aligned instance-level settings with connector configurations for Key Pair authentication, enabling successful crawling and correct retrieval of users and roles.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.8

Release6.3.5.8.6358c3a4e6a

23rd Jan 2026

Business Glossary

Fixed

Business Glossary Pagination Display Issue Resolved

In Business Glossary, an issue was identified in the EQ Bank production environment where pagination displayed “0 to 0 (out of 0)” even though entries existed in the database. The page incorrectly returned a zero record count, which also disabled the download option.

This issue has been resolved by correcting the handling of record counts. Pagination now shows the correct number of entries, and the download option is available as expected.

Impact Analysis

Fixed

Resolved Impacted Objects Download Error After Job Completion

In Impact Analysis, an issue where the download of the Impacted Objects list failed after job completion has been resolved. After a download job was completed, selecting the download link returned a 400 (Bad Request) error. This issue prevented access to the generated ZIP file.

The download failure was fixed to ensure successful file retrieval after job completion. The file generation logic was also updated to standardize the output format. Impacted Objects downloads now generate XLSX files, aligning with the rest of the application.

Build Auto Lineage

Fixed

Improved SAP HANA View Parsing Reliability

In the SAP HANA Connector, an issue where multiple view definitions failed to parse caused all 300 views to be marked as parse-failed in specific environments, even though most views worked with the same artifacts elsewhere.

This issue was resolved by validating and correcting the parse handling logic to ensure consistent view parsing across environments when using the same artifacts with SAP HANA.

Load Metadata from Files

New & Improved

LMDF-Based Configuration for Manual Qlik Sense Column Updates

An enhancement has been identified for the LMDF-based approach to support additional manual column update use cases in Qlik Sense. Previously, the solution addressed only limited scenarios and relied on a more rigid implementation, limiting extensibility and increasing the risk of functional gaps.

With this update, the LMDF solution will adopt a configuration-based design to enable controlled modifications to source metadata and support future expansion beyond Qlik. The feature is targeted for an initial release with Qlik, while remaining configurable for other reporting connectors. Updated documentation and LMDF templates will clearly define supported actions, object deletion behavior, and metadata modification rules. This approach improves consistency, reduces risk, and ensures predictable behavior for customers using LMDF-driven metadata updates.

Data Access Management

Fixed

Aligned Connector and Instance Settings for Snowflake RDAM

In Data Access Management, an issue where Snowflake RDAM crawling using Key Pair authentication did not fetch users and roles has been resolved. The connector-level Key Pair configuration was not reflected at the instance level. Required authentication fields were not visible, and instance details could not be edited. This issue prevented successful authentication during the crawl.

The instance-level configuration has been aligned with the connector settings. Key Pair authentication fields are now available and editable. RDAM crawling for Snowflake now correctly retrieves users and roles.

Hotfix Release6.3.5.9

This release introduces key improvements across Connectors and Service Desk, enhancing Bridge-based validation, connector reliability, and ServiceNow ticket creation.

Key Highlights

Connectors:

Enabled Bridge support for Data Access Management in the Snowflake connector, ensuring consistent validation and access management.
Fixed connector validation timeout issues in Bridge, reducing manual restarts and improving health check reliability.

Service Desk:

Resolved ServiceNow ticket creation failures by ensuring the Best Contact Method value syncs correctly for all supported options.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.9

Release6.3.5.9.635980f1c77

28th Jan 2026

Connector

New & Improved

Bridge Support for Data Access Management

In the Snowflake connector, the Bridge was not used for Data Access Management, even though the instance was successfully configured using key-pair authentication and permission crawling completed as expected. As a result, the Bridge field was not populated on the Instance page, preventing validation through the Bridge. This enhancement has been implemented. The Snowflake connector now uses the associated Bridge ID for validation, enabling proper Bridge-based Data Access Management and ensuring consistent access validation.

Fixed

Connector Validation Failing Due to Timeout Issues

In the Bridge, an issue occurred where connectors could not be validated due to timeout errors. As a result, users had to manually restart the Bridge service to validate connectors, and the Bridge health scheduler behaved inconsistently. This issue has been fixed. Connector validation is now handled more reliably, timeout behavior has been corrected, and error details are properly returned to the Bridge service.

Service Desk

Fixed

Best Contact Method Not Syncing During Ticket Creation

In the ServiceNow integration, an issue occurred where tickets were not created when the Best Contact Method was selected as Business Phone or Microsoft Teams. Although the Email option worked as expected, selecting the other options caused the field value to be sent as blank, resulting in ticket creation failure. This issue has been fixed. The selected Best Contact Method value is now passed correctly to ServiceNow for all available options, ensuring that tickets are created successfully regardless of the selection.

Hotfix Release6.3.5.10

This release introduces key enhancements across Build Auto Lineage, Service Desk Templates, Load Metadata from Files, Connectors, Data Access, Security, and Advanced Jobs, improving lineage accuracy, template stability, metadata consistency, connector capabilities, access control reliability, and job metadata updates.

Key Highlights

Build Auto Lineage: Fixed incorrect source mappings in Informatica PowerCenter lineage by incorporating both mapping and session-level configurations to accurately represent data flow.
Service Desk Templates: Resolved an issue where the Priority field became empty and non-functional after repositioning custom fields, ensuring consistent behavior regardless of layout changes.
Load Metadata from Files (Qlik Sense): Fixed a column deletion issue where objects marked for removal remained visible in the data catalog, ensuring permanently deleted columns no longer appear.
Connectors (BigQuery): Added query log support to capture SQL statements from BigQuery jobs, enabling lineage generation for SQL-based data movement and transformations.
Data Access (Snowflake): Corrected failures in role creation, account creation, permission grants, and row access policy associations, ensuring all access management operations now complete successfully.
Security – Applications: Fixed an issue where OvalSight remained visible after RBAC access was removed, ensuring application visibility now aligns with assigned roles and permissions.
Advanced Jobs (DBT → Delta Lake): Resolved missing column descriptions by ensuring metadata from DBT manifest files is properly applied to corresponding Delta Lake table columns during job execution.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.10

Release6.3.5.10.63510d2ccbb0

9th Feb 2026

Build Auto Lineage

Fixed

Corrected Source Mapping in PowerCenter Lineage

In Build Auto Lineage, an issue where Informatica PowerCenter lineage displayed incorrect source mappings has been resolved. Lineage was generated solely from mapping details, without considering session-level configurations. This issue caused lineage to show data flowing from an incorrect mapping instead of the actual session source.

The lineage extraction logic has been updated to evaluate both mapping and session details. Lineage now correctly represents the actual data flow and source locations.

Service Desk Templates

Fixed

Resolved Priority Field Issue in Service Desk Templates

In Service Desk Templates, an issue in which the Priority field became empty and stopped working after a custom field was dragged next to it has been resolved. The layout handling caused the Priority field to lose its values and behavior when positioned next to certain custom fields.

The template configuration logic was updated to ensure the Priority field displays correctly and functions as expected, regardless of custom field placement.

Load Metadata from Files

Fixed

Qlik Sense | Column Deletion Issue Resolved

In Qlik Sense, an issue in which crawled column objects marked for deletion via LMDF were reported as successfully deleted but remained in the application and appeared in the data catalog has been resolved. The deletion jobs completed without errors, but the columns persisted and remained visible in the data catalog. This issue caused a mismatch between the reported results and the actual metadata.

The deletion process has been fixed to ensure that columns marked for removal are permanently deleted and no longer appear in the data catalog.

Connectors

New & Improved

Query Log Support for BigQuery Connector

In the BigQuery connector, an enhancement has been made to support query log extraction for lineage generation. Previously, the connector did not capture SQL statement details from BigQuery jobs, limiting the ability to build lineage for SQL-based data movement activities.

With this enhancement, the connector can leverage the INFORMATION_SCHEMA.JOBS_BY_PROJECT view to retrieve executed SQL statements, including destination tables, referenced tables, and query text. These logs can then be processed within the application to establish lineage between source and target datasets.

This improvement enables lineage tracking for data movement scenarios where customers use INSERT INTO statements to transfer data between schemas (for example, from land to work). By capturing and parsing these query logs, the system can now support end-to-end lineage visibility for BigQuery-based transformations.

Data Access

Fixed

Resolved Snowflake Role and Permission Execution Failures

In Data Access Management, an issue where role creation, user creation, permission assignment, and row access policy association failed in Snowflake when initiated from the application has been resolved. Operations to create roles and accounts did not complete successfully. Permission grants on databases, schemas, and tables also failed. Row access policies could not be linked to tables. Deletion and permission revocation actions returned audit errors and did not complete as expected.

The connector authentication and execution logic have been corrected. Role and user creation now completes successfully. Permissions can be assigned and revoked on databases, schemas, and tables. Row access policies can now be appropriately associated with tables.

Security

Fixed

OvalSight No Longer Visible After Access Removal

In Security – Applications, an issue where OvalSight remained visible after Role-Based Access Control (RBAC) was enabled and authorized roles were removed has been resolved. OvalSight continued to appear even after access was disabled and roles were unassigned. This behavior did not match the expected access restrictions.

The access control logic has been corrected. OvalSight no longer appears after authorized roles are removed and access is disabled.

Advanced Jobs

Fixed

Resolved Missing Column Descriptions in Delta Lake Tables

In 'DBT File Parse And Update Description' AdvancedJob, an issue where column descriptions from the DBT manifest file were not transferred to Delta Lake table columns after job completion has been resolved. The job completed successfully, but descriptions defined in the manifest JSON were not applied to some corresponding table columns. As a result, certain columns remained without descriptions even though the metadata existed in the source file.

The update process has been corrected to ensure column descriptions from the DBT manifest are properly copied to the related Delta Lake table columns during job execution.

Hotfix Release6.3.5.11

This release introduces fixes and enhancements across Data Catalog, Lineage, Job Workflow, and Users & Roles, improving filter accuracy, lineage reliability, workflow efficiency, and team management flexibility.

Key Highlights

Data Catalog: Fixed schema filter behavior to exclude inactive schemas after regex-based crawls, ensuring only active schemas appear in filter selections.
Lineage (ADF): Fixed parsing logic to support long Sink expressions in Copy activities, enabling successful lineage generation for affected pipelines.
Job Workflow: Enabled execution of multiple Job Workflows in a single action, removing the previous limitation that restricted execution to one workflow at a time.
Users & Roles (Teams): Resolved editing restrictions for newly created empty teams, allowing updates, member assignments, and deletions regardless of team member status.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.11

Release6.3.5.11.635119f57948

16th Feb 2026

Data Catalog

Fixed

Corrected Schema Filter Behavior in Data Catalog

In Data Catalog, an issue where inactive schemas appeared in schema filters after a regex-based crawl has been resolved. After crawling a connection with specific schemas included via regex filters, some of those schemas were marked as inactive in the Security tab. However, these inactive schemas continued to appear in the Data Catalog table page under schema filters.

The filtering logic has been corrected to exclude inactive schemas from the Data Catalog schema filters.

Lineage

Fixed

Improved Handling of Long Sink Expressions in ADF Lineage

In ADF Lineage, an issue where lineage was not generated when the Sink of a Copy activity contained long expressions has been resolved. During pipeline validation, the parser failed to process extended expressions in the Sink configuration. As a result, lineage was not built for affected pipelines.

The parsing logic has been updated to handle long expressions in Copy activity Sink configurations correctly. Lineage now generates successfully for these pipelines.

Job Workflow

Fixed

Multiple Job Workflow Execution Support

An issue has been identified in the Job Workflow module where the Execute option is disabled when multiple Job Flow Names are selected. Currently, users can execute only one Job Flow at a time. When more than one workflow is selected via the checkbox, and the action menu (three dots) is opened, the Execute option is grayed out.

With this fix, users can select multiple Job Workflows and execute them in a single action. This improvement reduces manual effort when managing batch workflow executions.

Users & Roles

Fixed

Resolved Team Editing Restriction for Empty Teams

In Users & Roles | Teams, an issue that prevented newly created teams from being edited, assigned members, or deleted has been resolved. After creating a team, attempting to update the team description, add members, or delete the team triggered a pop-up message stating that there was a technical issue and to try again later. The issue primarily occurred in teams with no members. Teams that already had assigned members allowed updates to descriptions and additions of members without errors.

The underlying validation logic has been corrected to ensure teams can be edited, members can be assigned, and teams can be deleted regardless of member status.

Hotfix Release6.3.5.12

This release delivers important fixes across Connectors and Lineage, improving lineage accuracy, connector stability, and synchronization between OvalEdge and external systems. The update ensures reliable metadata extraction, accurate role synchronization, and improved report visibility across supported platforms.

Key Highlights

Connectors

Fixed Amazon QuickSight lineage building to temporary tables; lineage now correctly maps to actual relational tables.
Resolved Snowflake role and privilege synchronization issues, ensuring accurate reflection of roles and permissions.
Fixed Power BI crawl failures for specific report groups, improving metadata extraction reliability.
Resolved Power BI report preview and workspace visibility issues, ensuring reports and workspaces appear correctly when permissions are configured.

Lineage

Fixed schema visibility issue in Temp Lineage Correction, ensuring temporary table schemas display correctly.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.12

Release6.3.5.12.63512ea2f88b

2nd Mar 2026

Connectors

Fixed

Amazon QuickSight Lineage Building to Temporary Table Instead of Real Table

In the Amazon QuickSight connector, an issue occurred where lineage was built to a temporary table instead of the actual relational table. As a result, dashboards and analysis objects pointed to the temporary lineage table, and the dataset was not visible for correction or rerun on the build lineage page. This issue has been resolved. Lineage now correctly builds to the actual relational table, ensuring accurate dataset-to-table mapping and proper lineage representation.

Additionally, the schema visibility issue for temporary tables in the Temp Lineage Correction page has been addressed.

Snowflake Role and Privilege Synchronization Issues

In the Snowflake connector, role and privilege synchronization issues were observed during Key Pair authentication. Roles assigned to users in Snowflake were not reflected correctly in OvalEdge. Similarly, roles created from OvalEdge were not consistently visible in Snowflake. In some cases, granting certain privileges failed due to gaps in permission handling.

This issue has been resolved. Role assignments and privilege synchronization between OvalEdge and Snowflake now work correctly. Roles created from OvalEdge are properly reflected in Snowflake, and privilege grants are handled as expected.

Power BI Connector Crawl Failure for Specific Report Groups

In the Power BI connector, an issue occurred where crawling certain report groups failed, preventing successful metadata extraction. The crawl process terminated unexpectedly for specific report groups, even though permissions were correctly configured.

This issue has been resolved. The connector now handles such scenarios properly and continues processing without interruption. Report groups can now be successfully crawled, ensuring stable, consistent metadata extraction.

Power BI Report Preview and Workspace Visibility Issues

In the Power BI connector, an issue occurred where some reports could not be viewed in the Report Preview tab, and certain report groups or workspaces were not visible during the crawl/profile operation. This happened even though the required permissions were configured at the Power BI source.

This issue has been resolved. Reports and workspaces are now correctly detected and available for preview and crawling when appropriate permissions are set in Power BI. The connector now reflects newly granted workspace permissions as expected.

Lineage

Fixed

Schema Not Visible in Temp Lineage Correction

In the Lineage module, an issue occurred in which the schema of a temporary table was not visible on the Temp Lineage Correction page. Although the temporary table existed, the associated schema did not appear as expected. This issue has been resolved. The schema for temporary tables now appears correctly in the Temp Lineage Correction page.

Hotfix Release6.3.5.13

This release introduces enhancements and bug fixes across Data Catalog, Lineage, Data & Metadata Changes, and Connectors, improving view configuration flexibility, lineage completeness, metadata change tracking, and connector configuration visibility.

Key Highlights

Data Catalog: Fixed an issue where Viewer License users could not set public custom views as the default view. Eligible roles can now configure public views as the default, so the selected view loads automatically.
Lineage (Informatica PowerCenter): Resolved missing lineage for mappings that used temporary tables by correctly associating temporary tables with their corresponding cataloged tables.
Lineage (SAP BO): Improved lineage generation for SAP BO Universe aliases by linking alias references to their underlying data warehouse tables, ensuring complete lineage for reports.
Data & Metadata Changes: Added a download option for tracking metadata changes, allowing users to export object-level and column-level changes in structured formats such as CSV or Excel.
Connectors:
- Query Log Configuration: Fixed visibility issues so Query Log Settings now appear for both existing and newly created connectors.
- Cognos BI Connector: Fixed metadata extraction to capture report column expressions, including calculated expressions and distinct logic, ensuring accurate catalog and lineage representation.

Release Details:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.3.5.13

Release6.3.5.13.635130f3f687

10th Mar 2026

Data Catalog

Fixed

Resolved Default View Selection Issue for Viewer License

In Data Catalog, an issue where public custom views could not be set as the default view by accounts with Viewer License access has been resolved. Public views were visible, but the option to set them as the default view was unavailable. Role-based default view configuration also did not function as expected. As a result, a certain group of users had to manually switch views rather than using a predefined default

The view configuration logic has been updated to allow eligible roles to set available public views as the default view, ensuring the selected view loads automatically.

Lineage

Fixed

Informatica PowerCenter | Lineage Display Fix for Mappings

In Informatica PowerCenter, an issue where lineage was not displayed for certain mappings during lineage build has been resolved. Mappings that loaded data into cataloged tables were processed using temporary tables. Although the mappings were scanned successfully, the lineage was not reflected because the process did not associate the temporary tables with the original cataloged tables.

The lineage logic has been updated to correctly map temporary tables to their corresponding cataloged tables, ensuring that lineage is generated and displayed accurately.

Improved Lineage Mapping for SAP BO Universe Aliases

In SAP BO Reports, an issue where lineage was not built between SAP BO Universe aliases and their corresponding data warehouse (DWH) tables has been resolved. Aliases in SAP BO Universes act as references to actual warehouse tables. During lineage processing, these aliases were treated as final sources. As a result, lineage stopped at the alias level and did not connect to the underlying DWH tables. This issue caused incomplete lineage for reports that used aliases.

The lineage processing logic has been updated to correctly recognize alias mappings and link them to the corresponding DWH tables.

Data & Metadata Changes

New & Improved

Data and Metadata Changes | Download Option for Column-Level Metadata Changes

An enhancement has been requested in the Data and Metadata Changes module to enable downloading metadata change details in a structured format. Previously, object-level and column-level metadata changes were visible in the application interface, but users had no option to export this information for external analysis or reporting.

With this enhancement, users will be able to download metadata change details directly in a structured tabular format, such as CSV or Excel. The export will include object-level and column-level change information, allowing users to easily review schema modifications.

Connectors

Fixed

Query Log Settings Now Visible for Existing Connectors

In Connectors, an issue where Query Log Settings were not visible for existing connectors has been resolved. The settings were accessible when creating a new connector, but did not appear when viewing or validating previously created connectors. This issue prevented verification of the Query Log configuration for existing connections.

The connector configuration has been updated to ensure that Query Log Settings are visible and accessible for both existing and newly created connectors.

Cognos Connector | Improved Extraction of Report Column Expressions

In Cognos BI Connector, an issue where expressions defined in Cognos report columns were not captured during metadata crawling has been resolved. During the crawl process, calculated expressions and distinct logic present in report metadata were not extracted. As a result, these expressions were not visible in the corresponding columns or lineage.

The crawling logic has been updated to extract and capture report column expressions from Cognos metadata correctly. Calculated expressions and distinct logic are now properly reflected in the catalog and lineage.