Excel File to Sisense Integration

How Datrise loads Excel File into Sisense

Datrise syncs Excel File's worksheets, rows, columns, headers, cell ranges, and workbooks into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.

Ideal for embedded analytics on an in-memory engine.

Endpoints

Excel File: Spreadsheet workbooks from exports and shared drives.

Sisense: Analytics platform with elastic data models and embedded analytics.

How Excel File entities map to Sisense

Excel File entity	Sisense object	Notes
worksheets	`excel_file_worksheets`	id PK · custom fields → flattened columns for the cube
rows	`excel_file_rows`	id PK · linked to excel_file_worksheets
columns	`excel_file_columns`	id PK · linked to excel_file_worksheets
headers	`excel_file_headers`	id PK · linked to excel_file_worksheets

FAQ

How does Datrise handle Excel File's custom fields in Sisense?

Flexible values are stored as flattened columns for the cube, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Sisense types.

How does the Excel File to Sisense sync stay up to date?

It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.

Related pipelines

Early access

Connect Excel File to Sisense the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.