DatriseAI-first ETL

Platform Purple to Sisense Integration

AI-first ETL from Platform Purple into Sisense. Governed entities, incremental sync, typed landing tables.

How Datrise loads Platform Purple into Sisense

Datrise syncs Platform Purple's licenses, products, customers, activations, entitlements, and orders 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

Platform Purple: Software licensing, entitlements, and activations.

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

How Platform Purple entities map to Sisense

Platform Purple entitySisense objectNotes
licensesplatform_purple_licensesid PK · custom fields → flattened columns for the cube
productsplatform_purple_productsid PK · linked to platform_purple_licenses
customersplatform_purple_customersid PK · linked to platform_purple_licenses
activationsplatform_purple_activationsid PK · linked to platform_purple_licenses

FAQ

How does Datrise handle Platform Purple'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 Platform Purple to Sisense sync stay up to date?

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

Related pipelines

Early access

Connect Platform Purple 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.