Connectors

New & Improved

Microsoft Fabric OneLake Connector | New Connector Support

In the Connectors module, a new Microsoft Fabric OneLake connector has been introduced to integrate with Microsoft Fabric OneLake, enabling streamlined metadata management. The connector retrieves metadata from Microsoft Fabric workspaces, Lakehouses, folders, and supported file formats, supporting capabilities such as crawling, sample profiling, data preview, manual lineage, and Data Quality.

👉 For more details, see Microsoft Fabric OneLake section

Bridge Status | Enhanced Status Visibility and Failure Tracking

In the Bridge module, bridge restart, update, deployment, and recovery activities were not fully reflected in the Bridge Status interface. Status information lacked sufficient context to identify whether an operation was user-initiated, system-triggered, delayed, successful, or failed.

In addition, failures occurring during NAR package download and deployment were not clearly represented, making it difficult to determine the exact stage of failure during bridge update operations. The Bridge Status framework has been enhanced to provide comprehensive lifecycle visibility, improved operational monitoring, detailed failure reporting, and accurate status transitions across bridge activities.

These enhancements improve bridge observability, simplify troubleshooting, and provide a clearer view of bridge health throughout the update and operational lifecycle.

The following improvements have been implemented:

Component	Description
Status Framework	Enhanced bridge status tracking with standardized statuses including Running, Warning, Stopped, Restarting, Updating, and Inactive.
Mode Framework	Added Mode indicators to distinguish operations initiated by users, automated system processes, and external manual activities.
Heartbeat Monitoring	Implemented heartbeat-based monitoring to continuously evaluate bridge health and automatically identify healthy, delayed, inactive, and offline bridge states.
Heartbeat Threshold Tracking	Added automated status transitions based on heartbeat thresholds to accurately represent bridge availability and operational health.
Restart Lifecycle Tracking	Enhanced visibility into restart initiation, progress, completion, delay, recovery, and failure scenarios throughout the restart process.
Update Lifecycle Tracking	Added end-to-end monitoring for update operations, including initiation, execution, completion, delay detection, recovery, and failure handling.
NAR Download Failure Handling	Added detection and reporting of failures occurring during NAR package downloads from repository or storage locations.
NAR Deployment Failure Handling	Added validation and failure handling for NAR deployment activities, including file copy, permission, path, and storage-related issues.
Failure State Visibility	Enhanced bridge status reporting to clearly identify the exact stage of failure during update and deployment operations.
Status Transition Management	Improved status transition logic to ensure accurate representation of bridge activity during operational and maintenance events.
Error Reporting	Added meaningful status messages and detailed failure information to improve visibility into operational and deployment issues.
Detailed Logging	Enhanced logging across bridge update and deployment workflows to capture execution stages, failure reasons, and troubleshooting details.
Recovery Tracking	Added automatic recovery detection and status restoration when bridge communication resumes after delayed or failed states.
Deployment Safety Controls	Introduced safeguards to prevent inconsistent bridge states during incomplete or partially successful deployment scenarios.
Audit Tracking	Added tracking for bridge operations initiated through the application to improve operational traceability and change visibility.
Health Alerting	Added automated alert generation when Bridge health degrades or the Bridge becomes unavailable.
Downtime Monitoring	Implemented continuous monitoring to detect Bridge availability changes and downtime events.
Running Job Snapshot	Captured the list of running Bridge jobs during downtime to assist operational analysis and recovery.
Stakeholder Notifications	Added automatic notification support for configured recipients when Bridge downtime or health degradation is detected.
Alert Threshold Management	Implemented configurable alert thresholds to reduce unnecessary notifications during transient health events.
Operational Observability	Improved monitoring and visibility across bridge lifecycle events to support faster issue identification and operational support activities.
Troubleshooting Enhancements	Enhanced diagnostic information and failure reporting to reduce investigation effort and accelerate issue resolution.

👉 For more details, see the Bridge Status section

Profiling | Batch Profiling Standardization

In the Data Profiling module, profiling execution previously supported both the batch-based profiling implementation and the legacy/non-batch profiling flow through the enable.batch.profiling system setting. This dual execution path increased maintenance complexity and required continued support for fallback behavior. The legacy profiling flow has been deprecated and removed, and batch-based profiling is now the standard profiling implementation.

The following improvements have been implemented:

• Removed dependency on the enable.batch.profiling system setting

• Deprecated and cleaned up the legacy/non-batch profiling flow

• Fully enabled batch-based profiling as the default profiling implementation

• Validated batch execution for Row Count profiling and SQL profiling

👉 For more details, see Profile settings section

Amazon QuickSight | Dataset Crawl Log Messages

In the Amazon QuickSight connector, application logs previously displayed unnecessary dataset crawl messages for datasets without source code information, resulting in excessive log entries and reduced log clarity. The crawl process has been enhanced to correctly identify these scenarios and prevent inappropriate messages from being logged.

The following improvements have been implemented:

• Resolved inappropriate dataset crawl messages for datasets without source code information

• Added source code availability validation during dataset crawl processing

• Prevented unnecessary fallback log entries for supported crawl scenarios

• Improved log accuracy and reduced non-actionable log noise

• Standardized crawl logging behavior for reporting-based connectors

• Enhanced troubleshooting by ensuring logs capture only relevant crawl events

• Maintained existing metadata extraction and crawl functionality without impact to dataset synchronization processes

RDBMS Profiling | Row Count and Null Count for Skipped Columns

In the RDBMS Data Profiling, some columns were skipped due to data length constraints or skip profiling configurations. For these columns, Row Count and Null Count metrics were not generated. The functionality has been updated, and now Row Count and Null Count are captured even when detailed profiling is skipped for these columns.

The following improvements have been implemented:

• Columns excluded because of data length limits or profiling settings now include Row Count and Null Count metrics

• Profiling results now provide more complete metrics for all supported columns

• Columns that are eligible for detailed profiling continue to generate the complete set of profiling metrics

• Existing skip profiling rules continue to be applied without affecting the availability of core profiling metrics

👉 For more details, see Profile Rules section

Connector Draft Save | Save Progress

In the Connectors module, users were unable to save connector configurations without completing mandatory fields. The connectors can now be saved in Draft state with incomplete details.

The following improvements have been implemented:

• Enabled saving connectors in Draft status

• Allowed resuming connector configuration later

• Added UI indicators for incomplete connectors

• Supported partial configuration storage

👉 For more details, see the Set Up a Connection section

Salesforce (JWT Authentication) | Profiling Status for Warning Scenarios

In the Salesforce connector using JWT Authentication, tables that completed profiling with warning-level messages due to Salesforce platform limitations were previously displayed with the status "Profiled (Failed)". This status was misleading because profiling completed successfully and only non-critical warnings were encountered.

The profiling status handling has been improved to accurately distinguish between warning scenarios and actual profiling failures.

The following improvements have been implemented:

• Updated profiling status handling for warning scenarios

• Prevented warning-level conditions from being displayed as profiling failures

• Improved profiling logs for partially processed datasets

• Enhanced visibility into profiling results by distinguishing warnings from failures

• Maintained existing profiling functionality without impacting profiling execution

AWS Connectors | Connection Pooling

In AWS connectors, a new connection was created for each operation, causing high latency and inefficient resource usage. The enhancement has been implemented, and now connection pooling is enabled across AWS connectors.

The following improvements have been implemented:

• Implemented connection pooling for all AWS connectors

• Reused active connections to reduce overhead

• Added configurable pool size and timeout settings

• Improved performance and resource utilization

👉 For more details, see Connection Pooling section

Saved Connectors | Filter Enhancement

In the Connectors module, there was no filter option for Saved Connectors, making it difficult to manage large lists. The enhancement has been implemented, and now filtering is available for Saved Connectors.

The following improvements have been implemented:

• Added filter option for Saved Connectors

• Enabled filtering by connector attributes such as status and type

• Improved usability for connector management

• Enhanced search and navigation experience

Salesforce Picklist | Values Visibility

In the Salesforce Connector, picklist values were not visible in the Data Catalog, limiting reference data visibility. The enhancement has been implemented, and now picklist values are retrieved and displayed under Additional Metadata.

The following improvements have been implemented:

• Enabled retrieval of Salesforce Picklist Values during crawling

• Introduced “Picklist Values” subtab in Data Catalog

• Displayed values and default selection in tabular format

• Improved reference data visibility for users

👉 For more details, see Crawler Options section

Qlik QVD | Azure Ingestion

In the Qlik Cloud Connector, QVD ingestion was limited to local and remote sources, with no Azure Blob support. The enhancement has been implemented, and now QVD files can be fetched from Azure Blob Storage.

The following improvements have been implemented:

• Added Azure Blob Storage support for QVD ingestion

• Implemented secure authentication using Azure credentials

• Enabled listing and retrieval of QVD files via REST APIs

• Extended lineage processing for Azure-based QVD sources

Connectors Master | Unified View Page

In the Connectors module, connector details were scattered across multiple screens, reducing visibility of capabilities. The enhancement has been implemented, and now a unified Connectors Master Page is available.

The following improvements have been implemented:

• Introduced centralized Connectors Master Page

• Displayed connector details and supported features

• Improved discoverability of connector capabilities

• Enhanced UI consistency across connector views

👉 For more details, see All Supported Connectors section

Bridge Deletion | SAAS UI Support

In the SAAS environment, unused or inactive bridges could not be deleted from the UI, causing operational clutter. The enhancement has been implemented, and now bridge deletion is supported with validation and role-based access.

The following improvements have been implemented:

• Enabled UI-based deletion of inactive and disconnected bridges

• Restricted deletion to OE_Admin users

• Added dependency and job validation before deletion

• Retained audit logs for deletion actions

👉 For more details, see Manage Bridge section

QVD Azure | Blob Integration

In the Qlik Cloud Connector, Azure Blob Storage was not supported for QVD ingestion and lineage generation. The enhancement has been implemented, and now Azure Blob integration is available.

The following improvements have been implemented:

• Added Azure Blob Storage as QVD source

• Enabled OAuth-based secure authentication

• Supported automated QVD discovery and ingestion

• Improved lineage generation for cloud-based storage

Cognos Report | Curation Enhancement

In the IBM Cognos Connector, report curation required improved handling of semantic models and report components. The enhancement has been implemented, and now report curation supports structured metadata representation.

The following improvements have been implemented:

• Improved handling of report and semantic components

• Enhanced subreport and page-level metadata mapping

• Standardized report structure representation

• Improved consistency in report lineage output

SDK Primary Object | Manifest Update

In the connector SDK, the primary object definition was not standardized across connector manifests. The enhancement has been implemented, and now primary object support is available in connector configuration.

The following improvements have been implemented:

• Added primaryObject attribute in connector manifests

• Enabled automatic derivation of object types (TVC, R, DS, FF)

• Standardized connector object classification

• Updated generator UI and templates for consistency

Template UI | AI Prompt Management

In the platform, there was no UI to manage code templates and AI prompt templates for lineage extraction. The enhancement has been implemented, and now template management is available through a dedicated UI.

The following improvements have been implemented:

• Introduced UI for code and AI prompt template management

• Enabled upload and configuration of templates

• Added validation and error handling support

• Integrated templates with the backend storage system

👉 For more details, see the Lineage Template section

Fixed

IBM Cognos | Report Curation Fix

In the IBM Cognos Connector, report curation had inconsistencies in handling report components and semantic metadata. The issue has been resolved, and now report curation accurately reflects report structure and metadata relationships.

The following improvements have been implemented:

• Improved classification of active and inactive report objects

• Enhanced handling of semantic tables and subreports

• Standardized report-level metadata representation

• Improved consistency in report curation output

GreenPlum Profiling | External Table

In the GreenPlum Connector, profiling of external tables failed due to SQL syntax issues and driver limitations. The issue has been resolved, and now external table profiling executes without SQL grammar errors.

The following improvements have been implemented:

• Fixed incorrect SELECT COUNT(*) SQL syntax for external tables

• Resolved substring size limitation errors in JDBC driver

• Improved handling of external table profiling execution

• Ensured stable job execution for profiling tasks

Salesforce Validation Rules | Metadata Display

In the Salesforce Connector, validation rules were not available at table and column level in the Data Catalog. The issue has been resolved, and now validation rules are retrieved during crawling and displayed under Additional Metadata.

The following improvements have been implemented:

• Added retrieval of Salesforce Validation Rules during crawling

• Persisted validation rules with Salesforce objects

• Introduced “Validation Rules” subtab under Additional Metadata

• Enabled tabular display of rule details including formula and error message

Bridge Deletion | UI Management

In the SAAS environment, there was no option to delete unused or inactive bridges from the UI, requiring backend intervention. The issue has been resolved, and now bridges can be deleted directly from the application UI with controlled access.

The following improvements have been implemented:

• Added Delete Bridge option in Manage Bridge 9 dots menu

• Restricted deletion to OE_Admin and authorized users

• Added validation for active jobs and dependencies before deletion

• Enabled cleanup of bridge metadata after deletion

👉 For more details, see Manage Bridge section

Connector Rename | Audit History Capture

In the Connectors module, connector rename actions were not captured in Audit History, resulting in missing tracking of name changes. This issue has been resolved, and now connector rename actions are recorded in Audit History.

The following improvements have been implemented:

• Capture connector rename actions in Audit History

• Record previous and updated connector names

• Capture user and timestamp details for rename activity

• Display connector rename events under audit tracking history

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.