# Sisense - Lineage

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

<table><thead><tr><th width="219.333251953125">Configuration</th><th>Required Detail</th></tr></thead><tbody><tr><td>SQL Dialect Definition</td><td>SQL dialects must be defined in CrawlerOption.supportingDialects</td></tr><tr><td>Connection Priority</td><td>Connection priority for lineage must be defined in CrawlerOption.connectionsPriorityForLineage</td></tr></tbody></table>

{% hint style="warning" %}
An incorrect or missing configuration may prevent the connector from identifying the correct lineage path.
{% endhint %}

### Lineage Components

<table><thead><tr><th>Component</th><th align="center" valign="middle">Availability</th></tr></thead><tbody><tr><td>Dashboards</td><td align="center" valign="middle">✅</td></tr><tr><td>Widgets</td><td align="center" valign="middle">✅</td></tr><tr><td>ElastiCube Tables</td><td align="center" valign="middle">✅</td></tr><tr><td>ElastiCube Columns</td><td align="center" valign="middle">✅</td></tr><tr><td>Live Connect Tables</td><td align="center" valign="middle">✅</td></tr><tr><td>Import Queries (SQL)</td><td align="center" valign="middle">✅</td></tr><tr><td>Virtual/Semantic Tables</td><td align="center" valign="middle">✅</td></tr><tr><td>Renamed Columns</td><td align="center" valign="middle">✅</td></tr><tr><td>Temp Columns</td><td align="center" valign="middle">✅</td></tr><tr><td>Calculated Fields</td><td align="center" valign="middle">❌</td></tr><tr><td>File Sources</td><td align="center" valign="middle">✅</td></tr><tr><td>Relationships</td><td align="center" valign="middle">❌</td></tr><tr><td>Hierarchies</td><td align="center" valign="middle">❌</td></tr><tr><td>Filters</td><td align="center" valign="middle">❌</td></tr><tr><td>Parameters</td><td align="center" valign="middle">❌</td></tr></tbody></table>

## 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

<table><thead><tr><th width="220.6666259765625">Supported</th><th>Details</th></tr></thead><tbody><tr><td>Dashboard to Widget Lineage</td><td>Lineage extracted from dashboards to the underlying widgets</td></tr><tr><td>ElastiCube Table to Widget Lineage</td><td>Lineage extracted from ElastiCube tables to widgets</td></tr><tr><td>Live Connect Database to Dashboard Lineage</td><td>Lineage from live connection databases to dashboards</td></tr><tr><td>Import Query Lineage</td><td>SQL parsing and mapping for import queries</td></tr><tr><td>File-Based Lineage</td><td>Lineage from CSV and Excel files to dashboards</td></tr><tr><td>Column Transformations</td><td>Rename and add-column transformations</td></tr><tr><td>Semantic or Virtual Tables</td><td>Lineage for semantic or virtual tables</td></tr><tr><td>Wildcard Column Mapping</td><td>Mapping of fields when wildcard selection is used</td></tr></tbody></table>

{% hint style="info" %}
Column transformation lineage is supported only for rename and add-column actions.
{% endhint %}

### 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

<table><thead><tr><th width="219.3333740234375">Scenario</th><th>Limitation Description</th></tr></thead><tbody><tr><td>Calculated Fields</td><td>Complex expressions may not resolve fully</td></tr><tr><td>Derived Columns</td><td>Limited parsing for multi-step logic</td></tr><tr><td>Aggregations</td><td>Functions such as SUM and COUNT are not tracked as transformations</td></tr><tr><td>Dynamic SQL</td><td>Parameter-based SQL statements are not resolved</td></tr><tr><td>Cross-Cube Relationships</td><td>Not tracked in lineage</td></tr><tr><td>Encrypted Connections</td><td>The schema cannot be resolved without decryption</td></tr><tr><td>Missing Source Code Metadata</td><td>Lineage cannot be built without the required metadata</td></tr><tr><td>Dataset Lineage Status</td><td>Status may appear blank due to incomplete processing logic</td></tr></tbody></table>

{% hint style="warning" %}
Incomplete metadata or encrypted data sources can prevent lineage creation entirely.
{% endhint %}

### 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

<table><thead><tr><th width="220.666748046875">Not Supported</th><th>Description</th></tr></thead><tbody><tr><td>ElastiCube Relationships</td><td>Relationships or joins defined inside ElastiCubes</td></tr><tr><td>Hierarchies</td><td>Hierarchical field structures</td></tr><tr><td>Filters</td><td>Dashboard or widget-level filters</td></tr><tr><td>Parameters</td><td>Field parameters used inside queries or models</td></tr><tr><td>Cross-Dashboard Dependencies</td><td>Dependencies between multiple dashboards</td></tr><tr><td>Custom Scripts</td><td>Widget-level JavaScript or Python scripts</td></tr><tr><td>Multi-Step Calculations</td><td>Complex expressions such as nested CASE WHEN operations</td></tr><tr><td>Cross-Widget Column Dependencies</td><td>Columns derived through interactions between widgets</td></tr></tbody></table>

{% hint style="info" %}
Unsupported scenarios will not produce lineage and may appear disconnected in lineage visualization.
{% endhint %}

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ovaledge.com/connectors/connector-repositories/reporting-tool/sisense/sisense-lineage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.