v0.18

Feature Highlights

Query Parameters

Turn your maps into data applications! Add {{parameters}} to your SQL and UI inputs. Parameters are added to the URL, so you can share parameterized maps. Filter multiple queries with the same dimension using the same {{parameter}}.

Auto‐Save

Automatic map saving and sync between users. No need to press Save. Changes are synced and updated without page reload.

User Roles & Workspaces

Assign roles (viewer, editor, admin) to your collaborators and organize projects by workspace, making it easier to manage permissions and keep your maps organized.

Note: when migrating from previous versions all users and maps will be moved to "Default" workspace.

To fine-tune workspace permissions and default roles, we’ve added following configuration variables

• DEKART_ALLOW_WORKSPACE_CREATION

  • When set to true, users can create new workspaces. Set to false new users will be automatically added to Default workspace.

• DEKART_DEFAULT_WORKSPACE_ADMIN

  • Email that designates a default admin for Default workspace. When not provided all new users will be Admin. When provided all users will be viewers, unless specified differently with DEKART_DEFAULT_WORKSPACE_ROLE

• DEKART_DEFAULT_WORKSPACE_ROLE

  • Role assigned by default to new users (e.g., viewer, editor, admin). Requires DEKART_DEFAULT_WORKSPACE_ADMIN to be specified

Markdown README Support

Add READMEs to your maps and make them self-explanatory.

BigQuery Service Account Keys

Create connections using JSON service account keys—ideal when users don’t have direct BigQuery access or prefer not to rely on personal Google credentials.

Note: The DEKART_DATA_ENCRYPTION_KEY setting is required for this feature.
This key ensures secure storage of sensitive data, such as service account details.

DEKART_DATA_ENCRYPTION_KEY is an environment variable used to encrypt and decrypt sensitive information inside Dekart (for example, the JSON credentials for BigQuery). By setting this key, you enable Dekart to securely manage stored credentials.

Usage:

• Set DEKART_DATA_ENCRYPTION_KEY to a base64‐encoded, 32‐byte (256‐bit) encryption key.
• Dekart uses this key for all encryption/decryption operations related to credentials.

Steps to Generate & Set the Key:

1. Generate a Secure 256‐Bit Key
   Use a command like:

   openssl rand -base64 32

   This produces a base64‐encoded, 32‐byte key.

2. Add key to Google Secret Manager

3. Set the Environment Variable
   Add this key to your .env file or environment configuration:

   DEKART_DATA_ENCRYPTION_KEY=projects/121212121212/secrets/dekart-data-encoding-key/versions/1

With DEKART_DATA_ENCRYPTION_KEY in place, Dekart can securely handle BigQuery Service Account Keys and Snowflake credentials.

---

Other Notable Changes

• Click House Support, contributed by @Tsovak
• Allow Export: Toggle dataset downloads at the report level for tighter data control.
• Snowflake Improvements: Fixed re‐run errors, improved large download stability.
• Enhanced UI & Logging: Clearer error messages, better workspace screens, and more robust logs.
• Security Updates: Upgraded to Go 1.21, updated backend dependencies
• DEKART_GCP_EXTRA_OAUTH_SCOPES now also applied to OAuth tokens

---

Migration Guide

Important: always backup Postgres database before performing update

Note: when authentfication enabled, all current users and maps will be migrated to "Default" workspace. You can manage and rename via UX afterwords.

For all Docker-based deployments, update the docker tag, for example dekartxyz/dekart:0.17 -> dekartxyz/dekart:0.18

You’re all set! Enjoy the new features in Dekart 0.18.