What's New

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 account setting. 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

Markdown documentation makes every .md file in your project a first-class object. Previously, a Markdown file was only text: frontmatter appeared as raw characters, and docs were disconnected from the analytics they explained. Now, frontmatter renders as a Properties panel, while Markdown links connect docs to related documents, models, datasets, and dashboards.

This keeps business context, modeling logic, and decisions alongside the analytics they explain, rather than buried in separate wikis.

What you get:

• YAML frontmatter rendered as structured metadata, making key information easier to scan.
• Links to other Markdown files and Holistics objects, including models, datasets, and dashboards.
• AML source without leaving the doc - Ctrl+hover a resolved link to read its highlighted source.

The same metadata becomes the groundwork for AI retrieval: agents will be able to narrow to approved context before answering, instead of scanning the whole project.

Learn more: Markdown for analytics context

AI Anomaly Detection scans a time-series metric for statistically unusual data points, so you can quickly tell whether a spike or dip is worth investigating before a meeting.

Click Analyze in the chart toolbar and select Detect anomaly. Holistics AI:

• Looks at the metric's full history
• Builds an expected range from past data
• Flags any data points that fall meaningfully outside it

From there, you can save the generated chart directly to a dashboard to keep monitoring that metric over time.

This is part of Smart Analysis — and it pairs with Analyze Changes: once you know a movement is statistically unusual, you can dig into exactly what drove it, without leaving your dashboard.

Analyze changes lets you right-click any data point that looks off and find out why it moved without filing a ticket or waiting on an analyst.

Every follow-up question beyond "what is the number?" — whether a change is real, what drove it, which segments caused it — currently requires analyst support. Analyze Changes brings that investigation directly into your dashboard.

Right-click any data point and select Analyze increase or Analyze decrease. Holistics AI runs a two-step investigation:

1. Checks whether it's worth investigating — using historical data to determine if the drop or spike is statistically unusual, or just normal variance you can safely ignore.
2. Explains what drove it — breaking down which dimensions, segments, or regions contributed to the movement, and by how much.

The result: business users can answer "why did this change?" on their own, in a few clicks, right where they're already working.

Admins can now configure MCP access separately from in-app AI access, per user or group.

Previously, one combined toggle granted a user both AI access inside Holistics and AI access via MCP together.

Now, granting AI access to a user or group lets you choose the scope:

• In-app only: use AI inside Holistics.
• In-app & MCP: also connect an AI client like Claude directly to Holistics via MCP.

This helps you grant MCP access only to users you trust to use an external AI client responsibly.

Learn more: Who Can Use AI

Field Filters can now be built directly from a metric, the same way you'd build one from a dimension or measure.

What's changed​

Previously, Field Filters only supported dimensions and measures as the source field - even though metrics are a first-class concept in the semantic layer alongside them. Now you can filter on a metric too, for example only showing rows where a computed metric like Churn Rate crosses a certain threshold.

Learn more: Field Filters