What's New

Unified embedding is now available in Embedded Analytics. There is one way to embed: it's easy to start, you see value quickly, and you unlock more capabilities as your needs grow.

Why this matters​

Previously, you had to choose between two embedding methods before trying any embedded features:

• Single-dashboard embedding was quick to start but limited to viewing a dashboard. Adding data exploration, Ask AI, or email subscriptions meant migrating to Embed Portal.
• Embed Portal had every feature but needed a complex setup (portal, user attributes, publishing code) before you saw any value.

With unified embedding:

• Easy to set up: no need to create an Embed Portal, publish code, or set up user attributes.
• Effortless to scale: everything is set in the embed payload. New features unlock by adding config, never by migrating.

How it works​

1. Embed your first dashboard: generate one shared embed credential, sign a payload listing the dashboard, then load it in an iframe. The Embed Builder lets you preview it and copy the payload.
2. Add more features: unlock data exploration, Ask AI, user-built dashboards, email subscriptions, and more by updating the embed payload.
3. Use Embed Portal and dataset permissions when you need them: when listing every dashboard and permission rule in your app gets hard to keep in sync with Holistics, move them into an Embed Portal and attribute-based permissions in datasets.

Here's how each feature maps to a key in the payload:

Migrate from legacy single-dashboard embedding​

Your existing embed links keep working, so migrating is optional. To move to the new embed payload, follow the migration guide:

1. Swap the credentials: replace the per-dashboard credentials with the new shared credentials.
2. Name the dashboard in the payload: add the dashboard's name to objects.dashboards.

Learn more: Get started with unified embedding

Cross-filters are now saved in the dashboard URL. When you click a data point or row to cross-filter a dashboard, that selection stays in the link. Reload the page, bookmark it, or send it to a teammate, and you'll land on the exact same cross-filtered view.

What's new​

This update ensures that your cross-filter selections are seamlessly preserved across different viewing contexts.

• Works everywhere: internal dashboards, shareable links, and embedded dashboards.
• One link for the whole view: cross-filters are stored alongside your dashboard filters and controls, so a single URL captures everything you've applied.
• Nothing to set up: just cross-filter as usual and copy the URL.

Learn more: Cross-filtering | Passing Filter Parameters via URL

If a Databricks metric view already holds governed dimensions and measures, you can sync it into Holistics to build dashboards, implement embeds, and enable users to self-serve, without maintaining a duplicated definition.

At a high level, a Databricks metric view syncs into Holistics as a Table Model. Once synced, you can add the model to a dataset to build dashboards and embedded analytics.

Learn more​

• Databricks Metric Views

If a Snowflake semantic view already holds governed dimensions and measures, you can sync it into Holistics to build dashboards, implement embeds, and enable users to self-serve, without maintaining a duplicated definition.

At a high level, a Snowflake semantic view syncs into Holistics as a Table Model. Once synced, you can add the model to a dataset to build dashboards and embedded analytics.

Learn more​

• Snowflake Semantic Views

We've introduced an update: Exclude Endorse & Archive tags when duplicating objects.

Why this feature​

Endorse tells your team a piece of content is reviewed and trusted. Archive tells them it's no longer maintained. Neither should apply to a quick copy you're making to explore data personally.

What's new​

Now, when you duplicate or copy your dashboard, dataset or data model, then:

• Endorse and Archive tags are not copied to the new object.
• Other tags are copied over as before.

Learn more: Tags | Content Endorsement | Content Archiving

New navigation is coming to Holistics: one universal sidebar for the whole app. Dashboards, data, and tools now live in one place, with more room for your data, and the black header is gone.

Why this change​

We removed the legacy navigation structure that built up across past versions, and rebuilt the app around one cleaner and more consistent layout.

What's changing​

The sidebar is where you browse content, switch tabs, and find the key actions.

For data builders, Reporting and Development are now two clear modes in the sidebar. The sidebar stays in place while its content changes to match the mode you are in, so you can explore and build without losing your place.

What you see in the sidebar follows your role:

• Admins and analysts get both environments, with SQL editor, Embedded analytics, and Resources in the bottom section.
• Explorers get datasets and dashboards, with favorites, search, and create in the top row.
• Viewers get the dashboards they have access to, with favorites and search in the top row.

The new navigation arrives with the new dark mode, and together they give Holistics a more modern look and feel.

Version 4.0 workspaces get the new navigation by default. Earlier versions keep the current navigation for now.

Canvas dashboard's explicit_interactions list now states every active connection directly, so what's written is what's active, nothing is assumed.

Also, you can name target blocks directly across FilterInteraction, PopInteraction, and DateDrillInteraction without CustomMapping wrapper needed.

Before and after​

• ❌ Before (Old Syntax)

  // Old syntax - only the disabled links are visible, not the active connections
  interactions: [
    FilterInteraction {
      from: 'f1'
      to: [
        CustomMapping {
          block: ['v3', 'v4']
          disabled: true
        }
      ]
    }
  ]
  

• ✅ After (New Syntax)

  // New syntax - active connections stated directly
  explicit_interactions: [
    FilterInteraction {
      from: 'f1'
      to: ['v1', 'v2']          // Bare block names, no CustomMapping wrapper
      field: r(model.field)    // Set once on the entry, not per target
    }
  ]
  

Migration to new syntax​

We don't support mass conversion yet, but the transition is seamless:

• New dashboards automatically use the explicit_interactions: syntax.
• Existing dashboards convert when you next update their control or cross-filter setup.
• Legacy interactions: syntax remains functional, without breaking changes.

Learn more: AML Dashboard Interactions

Following the launch of dark mode, we're introducing light & dark mode dashboard theme.

How it works​

Each viewer sees Holistics in either light or dark mode, depending on their user settings. When you assign a theme to a dashboard, you can now choose how that theme responds to each viewer's mode:

• One theme for both modes: Everyone sees the same theme, regardless of their app mode.
• A theme per mode: Each viewer gets the theme matching their mode.

Learn more: Create & apply a theme | Syntax reference

Working long sessions in Holistics with a fixed light interface causes real eye strain. We've added dark mode as a personal preference:

• Switch between light, dark, or system mode at any time from your profile settings.
• The entire app updates instantly, including navigation, backgrounds, dialogs, and controls.

Your assigned dashboard theme stays static, but you can set separate themes for light and dark mode with light & dark mode dashboard theme.

Learn more: Switch to light/dark mode

Trace AI-triggered queries and jobs is now available across the Jobs API and warehouse query comments. You can now tell whether a query was triggered by AI, through which surface, and how the caller authenticated.

Previously, query metadata had no way to distinguish an AI-triggered query from a normal human-driven one, making it hard to attribute warehouse cost or audit usage by origin as AI usage grows.

Learn more: Trace AI-triggered queries and jobs