Sisense - Lineage Configuration
This article outlines the lineage coverage, configuration settings, metadata handling, supported scenarios, component behaviors, process flow, and known gaps for lineage extraction in Sisense. The lineage process captures how data moves from physical tables or files through ElasticCube and LiveCube data models to dashboards and widgets. It supports column-level and report-level lineage to show how fields progress and transform from origin to visual elements.
Lineage Configuration Requirements
Accurate lineage extraction depends on specific configuration settings. These settings must be defined correctly to ensure that data sources, SQL queries, and model structures are interpreted as expected.
Configuration Requirements Table
SQL Dialect Definition
SQL dialects must be defined in CrawlerOption.supportingDialects
Connection Priority
Connection priority for lineage must be defined in CrawlerOption.connectionsPriorityForLineage
An incorrect or missing configuration may prevent the connector from identifying the correct lineage path.
Lineage Components
Dashboards
✅
Widgets
✅
ElastiCube Tables
✅
ElastiCube Columns
✅
Live Connect Tables
✅
Import Queries (SQL)
✅
Virtual/Semantic Tables
✅
Renamed Columns
✅
Temp Columns
✅
Calculated Fields
❌
File Sources
✅
Relationships
❌
Hierarchies
❌
Filters
❌
Parameters
❌
Supported Use Cases
The connector supports several datasets and visualization lineage scenarios across different components of Sisense. These use cases describe areas where lineage extraction functions as expected.
Supported Lineage Scenarios
Dashboard to Widget Lineage
Lineage extracted from dashboards to the underlying widgets
ElastiCube Table to Widget Lineage
Lineage extracted from ElastiCube tables to widgets
Live Connect Database to Dashboard Lineage
Lineage from live connection databases to dashboards
Import Query Lineage
SQL parsing and mapping for import queries
File-Based Lineage
Lineage from CSV and Excel files to dashboards
Column Transformations
Rename and add-column transformations
Semantic or Virtual Tables
Lineage for semantic or virtual tables
Wildcard Column Mapping
Mapping of fields when wildcard selection is used
Partial or Limited Coverage
Certain scenarios function only with partial coverage due to limitations in metadata, query formats, or processing complexity. These areas may produce incomplete lineage results.
Scenarios
Calculated Fields
Complex expressions may not resolve fully
Derived Columns
Limited parsing for multi-step logic
Aggregations
Functions such as SUM and COUNT are not tracked as transformations
Dynamic SQL
Parameter-based SQL statements are not resolved
Cross-Cube Relationships
Not tracked in lineage
Encrypted Connections
The schema cannot be resolved without decryption
Missing Source Code Metadata
Lineage cannot be built without the required metadata
Dataset Lineage Status
Status may appear blank due to incomplete processing logic
Incomplete metadata or encrypted data sources can prevent lineage creation entirely.
Unsupported Scenarios
The connector does not support lineage extraction for certain components and modeling features due to the absence of accessible metadata or non-SQL-based logic.
Unsupported Lineage
ElastiCube Relationships
Relationships or joins defined inside ElastiCubes
Hierarchies
Hierarchical field structures
Filters
Dashboard or widget-level filters
Parameters
Field parameters used inside queries or models
Cross-Dashboard Dependencies
Dependencies between multiple dashboards
Custom Scripts
Widget-level JavaScript or Python scripts
Multi-Step Calculations
Complex expressions such as nested CASE WHEN operations
Cross-Widget Column Dependencies
Columns derived through interactions between widgets
Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA
Last updated
Was this helpful?