Visma e-conomic to Databricks SQL Warehouse Integration
AI-first ETL from Visma e-conomic into Databricks SQL Warehouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Visma e-conomic into Databricks SQL Warehouse
Datrise syncs Visma e-conomic's invoices, customers, suppliers, journal entries, accounts, and products into Databricks SQL Warehouse as a Delta Lake table per source entity. Flexible or custom fields land in VARIANT or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses a Delta MERGE on stable id, with change history available via time travel, so re-runs update only what changed. Delta partitioning by load date with OPTIMIZE/Z-ORDER on query keys. Datrise writes Unity Catalog–governed Delta tables, so lineage and permissions are managed centrally rather than per-notebook.
Ideal for lakehouse analytics and ML feature tables on Databricks.
Endpoints
Visma e-conomic: Nordic accounting, invoicing, and ledger records.
Databricks SQL Warehouse: Lakehouse SQL endpoints over Delta tables.
How Visma e-conomic entities map to Databricks SQL Warehouse
| Visma e-conomic entity | Databricks SQL Warehouse object | Notes |
|---|---|---|
| invoices | visma_e_conomic_invoices | id PK · custom fields → VARIANT or STRUCT columns |
| customers | visma_e_conomic_customers | id PK · linked to visma_e_conomic_invoices |
| suppliers | visma_e_conomic_suppliers | id PK · linked to visma_e_conomic_invoices |
| journal entries | visma_e_conomic_journal_entries | id PK · linked to visma_e_conomic_invoices |
FAQ
How does Datrise handle Visma e-conomic's custom fields in Databricks SQL Warehouse?
Flexible values are stored as VARIANT or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Databricks SQL Warehouse types.
How does the Visma e-conomic to Databricks SQL Warehouse sync stay up to date?
It runs incrementally — Datrise uses a Delta MERGE on stable id, with change history available via time travel.
Related pipelines
More destinations for Visma e-conomic
- Visma e-conomic → ClickHouse
- Visma e-conomic → DuckDB
- Visma e-conomic → Amazon Athena
- Visma e-conomic → Amazon S3 Data Lake
- Visma e-conomic → Azure Data Lake Storage
- Visma e-conomic → Azure Synapse
- Visma e-conomic → Spreadsheets
- Visma e-conomic → Airtable
- Visma e-conomic → CSV Files
- Visma e-conomic → MongoDB
- Visma e-conomic → Supabase
- Visma e-conomic → Neon
More sources for Databricks SQL Warehouse
- Vitally → Databricks SQL Warehouse
- WaiterAid → Databricks SQL Warehouse
- Weatherstack → Databricks SQL Warehouse
- Webflow → Databricks SQL Warehouse
- WooCommerce → Databricks SQL Warehouse
- Workable → Databricks SQL Warehouse
- Workday RaaS → Databricks SQL Warehouse
- WorkRamp → Databricks SQL Warehouse
- Wrike → Databricks SQL Warehouse
- Yandex Metrica → Databricks SQL Warehouse
- Younium → Databricks SQL Warehouse
- YouTube Analytics → Databricks SQL Warehouse
Early access
Connect Visma e-conomic to Databricks SQL Warehouse 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.