Skip to main content

54 posts tagged with "new-feature"

View All Tags

๐Ÿ“ Markdown: updated to be part of your analytics

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

๐Ÿค– Anomaly Detection

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.

๐Ÿ”’ Redact data for AI

AI reading a chart with the email column redacted

You can now redact data for AI.

Admins and Customer Success reps often need PII access to do their jobs - but that shouldn't mean AI gets it too. Previously, AI inherited the full permissions of whoever asked it a question, with no way to hold it to a stricter standard.

Now, you can configure your semantic layer so sensitive data stays visible to the people who need it and out of reach for AI, no matter who's asking.

Learn moreโ€‹

๐Ÿ—‚๏ธ File history: trace and restore any file

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

๐Ÿ“Š Custom chart as code

Custom charts now live in AML. With this update, you can define them as code, create them through a GUI, and preview against real data:

  • Define as code: Create a CustomChart 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.
  • Easy creation flow: Create a new chart in seconds with three simple starting points: chat with AI to generate it, pick a pre-made template, or build it from scratch.
  • 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 (non-as-code) custom charts in Admin Settings remain accessible for viewing, editing, and deletion, but new charts must be defined in AML. To migrate, use the Copy as code option in Admin settings > Custom charts.

Learn more: Custom charts | AML syntax reference

๐ŸŽจ Theme-level color palette

Color palettes can now be assigned at the theme level. With this update, you can:

  • Apply color palette at theme level: Assign a palette to a theme so all charts on that dashboard use it automatically, eliminating the need for per-chart overrides. The palette also carries through to:
    • The theme thumbnails, so you can preview color palette before applying.
    • The explore modal, where charts inherit the dashboard theme's palette by default.
  • Override at chart level: Individual charts can still set their own palette when needed.

Learn more: AML theme reference

๐ŸŽฏ Chart suggestion: Stay focused on your data, not your chart setup

Chart Suggestions is now live in Explore. Select your fields and instantly get up to 3 chart recommendations tailored to your data โ€” apply any of them in one click, so you can stop thinking about chart setup and start thinking about your data.

This is part of a bigger push to make Explore faster for everyone. Auto-mapping already takes care of slot assignment. Chart Suggestions now tells you which chart to reach for. And we're not done yet โ€” next up: switch between chart types without losing your field configuration. Stay tuned.

Give it a spin and let us know if the suggestions are hitting the mark!

๐Ÿ—„๏ธ Reusable Library in Reporting Dashboard Editor

Demonstration of browsing and inserting a shared component from the Reusable Library in Reporting.

Browse and insert reusable components directly in the Reporting dashboard editor - no need to switch to Development.

Previously, inserting library components required switching to Development, which added friction and blocked Explorers entirely. Now you can insert existing components right where you work - components built by one teammate are instantly available to everyone.

Learn more: Reusable components

๐ŸŽจ Define color palettes as code

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