Release Notes

Why this feature?​

Writing clear, descriptive PR titles and messages takes time and mental energy. Analysts often face writer's block when creating pull requests, leading to rushed or incomplete descriptions. This results in poorly documented changes that make code reviews harder.

How it works​

• Smart Generation: AI analyzes your code changes and automatically creates a clear title and detailed description
• One-Click Usage: Accept the suggestions instantly or customize them to your needs
• Context-Aware: Captures important details you might forget to mention

Before vs After​

Before (Manual Process)

• Manually craft a descriptive title and message.
• Spend time recalling and documenting all changes.
• Risk inconsistent or incomplete descriptions.

After (AI-Powered)

• AI instantly generates a clear title and detailed message.
• One-click to accept the suggestions or customize them.
• Ensure every PR has consistent, high-quality documentation.

Key Benefits​

• Faster PRs - No more writer's block when creating pull requests
• Better Documentation - AI catches details you might forget to mention
• Consistent Quality - Every PR gets a well-structured title and description
• Time Savings - Spend less time on admin work, more time on analysis

Getting Started​

To use this feature, you need to:

1. Join the Alpha Program - Sign up for Holistics AI access
2. Connect to GitHub - Integrate with your GitHub repository
3. Enable PR Workflow - Activate the PR Workflow for your organization

Once enabled, the AI will automatically generate titles and descriptions for all new pull requests in your workflow.

🔥 Why this feature?​

Some of our customers were struggling with cryptic field reference errors that only showed up when trying to publish dashboards. No clear error messages, no way to navigate to problems, and broken references went undetected when fields were renamed. This was creating a poor developer experience and blocking teams from scaling their analytics.

💡 How it works​

• Real-time validation: Field reference errors now show up immediately with red underlines as you type
• Click-to-navigate: Click on errors to jump directly to the problematic code
• New r() syntax: Use r(users.id) instead of ref('users', 'id')

Before vs After​

❌ Before (Old Syntax)

// Old syntax - prone to typos, no IDE support
VizBlock {
  label: 'Revenue by Category'
  viz: PieChart {
    dataset: 'ecommerce'
    legend: ref('products', 'category')  // No validation
    series {
      field {
        ref: ref('orders', 'revenue')    // String-based, error-prone
        aggregation: 'sum'
      }
    }
  }
}

// 😰 Common issues:
// - Typo: ref('product', 'category') → No error until runtime
// - Renamed field: orders.revenue → orders.total_revenue → Broken reference
// - No autocomplete or navigation support

✅ After (New Syntax)

// New syntax - validated, IDE-friendly
VizBlock {
  label: 'Revenue by Category'
  viz: PieChart {
    dataset: 'ecommerce'
    legend: r(products.category)         // Real-time validation 
    series {
      field {
        ref: r(orders.revenue)           // Click to navigate to definition
        aggregation: 'sum'
      }
    }
  }
}

// 🎉 Benefits:
// - Typo: r(product.category) → Immediate red underline
// - Renamed field: Automatic detection of broken references
// - Full IDE support: autocomplete, go-to-definition, find usages

👀 Migration to new syntax​

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

• New dashboards automatically use the new r(model_name.field_name) syntax
• Existing dashboards convert to new syntax whenever you edit and save a widget
• Old syntax still works - no breaking changes.

We’ve deprecated Explore Data (basic mode) to unify the experience - now in just a single Explore Data interface.

Alongside this, Explore Data now can Explain Chart - a new capability that helps you easily understand visualizations with clear, concise explanations of trends and patterns. It makes charts easier to interpret, so users can act on insights with more confidence.

🌟 More powerful, easier to use - now all in one place.

📥 Interested in Holistics AI? Join the waitlist and start exploring a new way to work with data.

We're building Content Archiving, a powerful new feature that allows you to hide outdated analytics content. This keeps your workspace clean while preserving full access to your historical data.

The Problem We're Solving​

A growing analytics workspace often becomes cluttered with outdated reports and dashboards, making it difficult to find current, relevant information.

The Solution​

Content Archiving provides a clear way to streamline your workspace and ensure data accuracy:

• Organized and fresh workspace: We hide outdated content from views, searches, and reports, ensuring a clean workspace and that users only see current, relevant data.
• Preserve history: You'll maintain full access to all archived data for reference.

For details, visit our public documentation: Content Archiving

Timeline​

This feature is planned for release in Early September. 🚀

We're introducing a new Pull Request (PR) workflow to help organizations maintain quality and control over their dashboard changes. This feature empowers administrators to implement a robust review process before changes go live.

Why We Built This​

Have you ever discovered unexpected changes in your production dashboards? While you can track down who made the changes, by then the damage is already done.

The root cause? A lack of mandatory review process for dashboard changes. Without proper oversight, unrestricted publishing can compromise your project's reliability and integrity.

Key Features​

The new PR Workflow includes:

• Company-wide Control: Administrators can enable/disable the PR Workflow for their entire organization
• Review Management: Administrators and Dashboard Owners can review all changes before they go live
• Streamlined Process for Analysts:
  • Easy submission of changes for review
  • Automatic publishing after PR approval and merge
  • Instant notifications if any errors occur during publishing

For detailed information, check out our PR Workflow documentation.

You don’t need a national survey to know that most data teams rebuild the same charts again and again across different dashboards. We’ve all been there, staring at a new dashboard request and thinking "I know we've built something like this before..."?

Your best dashboard components deserve to live multiple lives, not buried in some report from last quarter, waiting to be rebuilt from scratch.

With Reusable Component Library, every visualization you create can become a building block for future dashboards. Think of it as your team's collective intelligence, transformed into drag-and-drop components. When you need it again, simply grab it from your library, tweak it, and you're done.

For more information, please visit our documentation.

We're excited to announce Content Endorsement has been officially launched, a feature that provides your organization a powerful way to mark trusted and reliable content.

The Problem We've Solved​​

As analytics content grows across your organization, users often struggle to identify which reports and dashboards are reliable and current. Without clear indicators of content quality and status, teams waste time on outdated materials and lack confidence in their data-driven decisions.

The Solution​​

By offering Content Endorsement features, we help data teams mark trusted content. Users can easily identify reliable, recommended content.

Documentation​

For more details, please refer to our public docs: Content Endorsement

Why Spreadsheet Analysis Is Still A Pain​

Picture this: It's Monday morning, and your stakeholder needs insights from that customer survey data sitting in a spreadsheet. Or maybe you want to combine your CRM export with existing metrics for a one-time analysis. In traditional BI setups, you're looking at:

• Waiting for data engineering resources
• Complex ETL pipeline setup for temporary data
• Database permissions and access hurdles
• Hours or days before you can start analyzing

What if you could skip all that and go straight to insights?

The Solution: Import CSV/Google Sheets Through Holistics​

Imagine this instead: You drag your CSV file into Holistics, and it loads straight into your database. Within seconds you're building charts and dashboards.

No IT tickets, no manual setup, no waiting around.

We're working on seamless CSV and Google Sheets import that drops your data directly into your existing warehouse, automatically creates data models with proper field types, and lets you start analyzing immediately.

Your data stays in your own infrastructure, gets proper validation and configuration. You can also re-upload your source file to keep things fresh. From raw file to actionable insights in a minute.

Want early access? Reach out to us via a support ticket!

Introduction​

In some scenario, you want to point the dashboards to different data source (database or data warehouse) dynamically, based on who's viewing the report or whether it's in production or dev mode.

Thanks to its programmable nature, Holistics can support this capability natively. This will enable popular use cases such as:

• Clients Dashboarding: Build the same set of models/datasets/dashboards for clients but different data source for each client underneath.
• Dev/Prod environment: Dynamically switch the underlying data sources (from dev → prod and vice versa) based on the environment that analysts are working on
• Dynamic data sources for embedded analytics: Embedded analytics but different customers use different databases.

Demo​

For more information, please refer to our doc about Dynamic Data Sources

To follow up on the Dynamic Data Sources feature, this is another cool feature that might be useful, dynamic schemas

📊 ​Dynamic Schema for Dev/Prod Environments​​

For those of you who separate dev and prod environments based on schema (or datasets in BigQuery) instead of the actual data source, we’ve got you covered with our Dynamic Schema option.

This feature lets you switch schemas easily using basic string interpolation in your model's table_name property.

Here’s a quick example to show how it works:

// This is for dynamic schema use case by branch  

const current_branch = H.git.current_branch
              
const dynamic_schema = 
  if (current_branch == 'master') { 'prod' } 
  else if (current_branch == 'staging') { 'stg' } 
  else { 'dev' }

// in Table Model
model users {
  type: 'table'
  data_source_name: 'your_db'

  // dynamic schema in table name
  table_name: '${dynamic_schema}.users'
}

// in Query Model
model derived_users {
  type: 'query'
  data_source_name: 'your_db'
  
  // dynamic schema in a query
  query: @sql select * from ${dynamic_schema}.users ;;

}