43 posts tagged with "new-feature"

Reusable Library is coming to Reporting — browse and insert shared components directly in the dashboard editor, no need to switch to Development.

Previously, using library blocks required switching to Development, which added friction and completely blocked explorers. With this update, you can insert existing library components right where you work. Blocks built by one team member are instantly available to everyone.

Learn more: Reusable Components

Timeline​

Expected by end of March 2026.

AI-powered Dashboard Summaries will automatically generate and save a short narrative alongside your dashboard — highlighting key trends, notable changes, and actionable insights.

Stakeholders who don't have time to interpret every chart get the story at a glance. Dashboard owners get a consistent written summary that updates with the data, instead of writing one by hand each reporting cycle.

AI Development Copilot is now in beta. Analysts can ask the copilot to build datasets, wire up dashboards, or edit any code file in Development — without leaving the editor.

Previously, building out a semantic layer meant hand-writing AML file by file. The copilot takes care of the repetitive parts: scaffolding models and datasets, adding relationships, translating a sketch into a canvas dashboard, or refactoring a messy field definition. You stay in charge — review the diff, tweak, commit.

Learn more: Build datasets with AI

Organization-level AI Memory will let admins promote useful insights from individual users' AI memory up to the organization level — surfacing suggestions to improve the semantic layer and dashboards based on real usage patterns.

Today, AI memory is per-user: what one analyst teaches the AI stays with that analyst. Promoting it org-wide means the whole team benefits. Over time, AI gets smarter for everyone, grounded in how your organization actually analyzes data.

AI Usage Analytics will give admins visibility into AI adoption across the organization: who is using AI, what types of questions get asked, and how usage trends over time.

This helps you measure ROI, identify training opportunities, and understand which teams get the most out of AI — so you can double down where it's working and unblock teams where it isn't.

Custom embedded app theme is coming to the Embedded Portal in Q3 2026. Admins will be able to fully customize how Holistics looks inside their host app - matching brand colors, dark mode, and visual identity across the entire embedded experience.

Previously, embedded Holistics always rendered in light mode regardless of the host app's theme or brand colors. Now you can pass visual context via the embed payload and Holistics will adapt accordingly.

What's included:

• App theme: Configure colors for UI elements inside the iframe (navigation bar, dashboard header, AI panel, etc.) via embed payload
• Dashboard theme: Dynamically apply a pre-configured dashboard theme to all embedded dashboards via embed payload

Timeline​

This feature is currently in development and expected to be available in Q3 2026.

Learn more: Embedded Portal

Custom chart definitions are moving into AML, so you can define them as code alongside your models, dashboards, and themes.

With this update, you can:

• Define charts as code: Create a custom chart block in a .chart.aml file. This lets you version-control your chart definitions in Git, validate their syntax, and protect them with dependency checks to prevent accidental deletion.
• Preview while editing: As you write chart code, a preview panel renders the chart against real data. This lets you see and debug the output without leaving the editor.

Legacy custom charts in Admin Settings continue to work. Going forward, define new custom charts in AML.

Learn more: Custom charts | AML syntax reference

Timeline: Est. Q3 2026

File history gives every file - dashboards, models, datasets - its own version timeline. See every version of a file with who changed it, when, and why, then restore just that file to any past version without reverting anyone else's work.

Previously, rolling back a past version worked at the project level: restoring reverted the entire project, including teammates' unrelated changes since then. Now you can scope a rollback to a single file. You can also duplicate a past version into a new file to compare side by side, or jump to the full project history to see everything that changed together.

Learn more: File History & Restore

Working long sessions in Holistics with a fixed light interface causes real eye strain.

This is why we're introducing dark mode as a personal preference. Users will be able to switch at any time, and the change will take effect across the entire app at two levels:

• App level: When a user switches modes, the entire app updates instantly, including navigation, backgrounds, dialogs, modals, filter panels, and controls.
• Dashboard level: For each dashboard, builders can map a specific theme to each app mode so the dashboard visuals update dynamically as users toggle. For dashboards that should always look the same regardless of mode, builders can configure a fixed theme to render consistently.

Timeline: Est. End of July 2026

Color Palettes are now as-code, meaning you can define and manage your palettes directly within your AML workspace. Now you can:

• Define as code: Create palettes in palette.aml once and reference them anywhere, with full version control.

• Set a workspace-level default: Mark a palette in settings.aml so charts automatically use it by default, unless overridden at the theme or visualization level.

(*) Legacy palettes remain usable and deletable, but they can no longer be edited. To update a legacy palette, recreate it in AML.

Learn more: Color palettes | AML syntax reference