Release 5.6
Discover what’s new in Tellius 5.6—a major release packed with HAVING clause support, per-group Top N queries, measure-aware date filtering, smarter conditional formatting, and a sleek Kaiya redesign.
Tellius 5.6 breaks through key analytical bottlenecks with query processing capabilities and enterprise-grade access controls.
The release introduces native
HAVING
clause support for post-aggregation filtering, "for each" group-wise ranking across all query interfaces, and hierarchical pivot tables with automatic rollup calculations.Performance optimizations include pushdown query execution, intelligent auto-range global filters, and lightweight Kaiya integration within the Assistant interface.
Additional operational improvements include moving percentage calculations with fallback logic for missing periods, and enhanced conditional formatting with cross-metric comparisons.
🚀 New features
Support for “HAVING” clause in natural language queries
Kaiya now supports post-aggregation filtering using the HAVING clause, enabling more powerful and precise queries. This allows you to apply conditions after grouping, ideal for analyzing top performers, outliers, or applying threshold logic.
WHERE filters raw rows before aggregation. Example: “Show me accounts where sales > $100K” → filters individual transactions.
HAVING filters after aggregation. Example: “Show me accounts where total sales > $100K” → filters based on total sales per account.
Kaiya intelligently applies this logic using pushdown optimization, ensuring efficient execution and faster performance—no extra steps or complexity for the user.
“For each” query support in Search, Kaiya, and Vizpads
You can now use “for each” logic in Search, Kaiya, and Vizpad to get accurate per-group rankings—like “Top 5 products for each state.” Previously, you might get top results across the entire dataset, without considering group-wise breakdowns. This release introduces native support for "top/bottom n" within a dimension, so you can now correctly identify the top 10 HCPs per region, top 3 accounts per territory, or highest-performing HCOs per month—accurately and at scale.
In Vizpads, a new checkbox in Top N/Bottom N filters lets you apply ranking logic “within” each group of the chosen dimension. For charts, the primary dimension drives the group logic; in tables, it uses the first listed dimension. In Search and Kaiya, you can just ask “Top 5 customers for each month” or “Bottom 10 products per region” and Tellius will compute results per group as expected. This unlocks a whole class of insights that were previously manual or hacky to build. Sales teams, territory planners, and pharma analysts will especially benefit—now able to instantly spot regional or segment-specific leaders and laggards without writing custom logic or splitting queries.

Pivot table enhancements
The pivot table experience just got a major upgrade in Tellius 5.6, introducing hierarchical grouping, flexible layouts, and grand total support. All these enhancements will be available once you enable the "Use Advanced Pivot" toggle in the Configuration pane.
You can now create nested, multi-level hierarchies in your pivot tables (for example, Region → State → City) displayed in a tree-like structure that lets you progressively expand or collapse levels. This works for both rows and columns. Additionally, columns can be pinned and autosized.
You can now generate grand totals for both rows and columns in pivot tables. In hierarchical tables (Region → State → City), Tellius automatically calculates rollups at each grouping level, so you can view totals for regions, states, and cities without manual configuration.

Auto-range global filters
In Vizpads, applying global filters is now significantly easier—users no longer need to manually define filter conditions to be applied across the Vizpad. Tellius intelligently pre-populates sensible defaults:
Measures: Automatically sets the filter range using the minimum and maximum values from the dataset
Dimensions: Defaults to “in” operator
Dates: Uses the full min-to-max date range from the dataset
Date Filter: Lets you turn on/off date-based filtering independently of other filters

Together, these changes remove friction in dashboard setup and make global filtering more intuitive—especially useful when building dashboards collaboratively or deploying at scale. Users can apply filters faster without second-guessing system defaults or manually reconfiguring common conditions.
Measure-aware date filtering
In Tellius 5.6, we’ve introduced measure-date alignment mapping to make relative date filters more intelligent and context-aware—especially when you're working with datasets that have multiple date columns. When your datasets refresh on different schedules, "last month" can mean different things for different measures. You can now define date mappings at the Business View level by linking each measure (e.g., Revenue, Gross Sales) to its appropriate date column (e.g., order_date, signup_date). This ensures your filters are applied using the correct date context. For example, if sales data is current only through January 2025, but call data is available through February 2025, applying “this month” to a sales metric will correctly filter to January—preventing misleading “No Data” results.

To get started:
Navigate to Data → Business View → Date Mapping to define your measure-date mappings.
In the filter panel of Vizpads, enable the Use Preset Date Ranges toggle (after enabling Date filter toggle). When enabled, date filters follow measure-date columns mapping configured in the Business View. This ensures any applied date filters are aligned with their corresponding measures.
This feature helps you and your team build dashboards that reflect the actual reporting cadence of your business and auto-align to each measure's freshest data.
Row-Level Policy (RLP) support in Feed
Feed alerts that are shared now fully honor Row-Level Policies (RLPs), ensuring recipients only receive alerts relevant to the data they're authorized to access.
You can now share feeds with distribution lists or access-controlled user groups directly from the sharing options, making it easier to manage alerts at scale. When a feed alert is triggered, Tellius dynamically evaluates the condition based on each recipient's data access rules.

For example, if you share a feed tracking a 20% drop across all brands with users from different groups: 3 from User Group A (Brand X access), 2 from User Group B (Brand Y access).
Send alerts to User Group A members only if Brand X sales drop 20%
Send alerts to User Group B members only if Brand Y sales drop 20%
If someone belongs to both Group A and Group B, they get alerts when either Brand X or Brand Y sales drop 20% (because they can see both brands' data)
Each recipient's RLP is evaluated at runtime, so the same feed behaves differently depending on each person's access level—eliminating the need to duplicate feeds per role or access level.
This is applicable for all existing and newly created Feed alerts.
Kaiya design upgrade
We’ve given a design uplift to Kaiya, Feed and homepage—making it more elegant, focused, and visually crisp. Expect:
A cleaner tracked metrics section with tighter spacing
A more intuitive query input area for faster interaction
A reorganized popular queries panel for easier discovery

You can now trigger insights directly from Kaiya when working with Live BVs. This expands Kaiya’s ability to generate on-the-fly analyses, making real-time exploration even more seamless.
Expanded group sync support for external IdPs
Tellius 5.6 introduces support for syncing user groups from LDAP. Previously, group synchronization was limited to Azure AD.
With this enhancement, organizations using LDAP directories can now leverage the same group-level access, role mapping, and user provisioning capabilities previously available only with Azure AD.

📈Enhancements
Smarter conditional formatting for your business logic
You now have more flexibility when applying conditional formatting in Pivot Tables. With this release, you can define rules that compare values across grouping levels, metrics, or time—all without needing calculated columns or manual aggregation.
Here’s what’s new:
Formatting based on different levels of data You can now evaluate formatting rules against aggregated values at any dimension level—such as Region, State, or County. For example, instead of comparing each state's revenue to the overall average, you can highlight states where revenue exceeds the average within their region. This logic is defined directly in the formatting configuration panel.
Formatting based on fixed value or another metric Conditional logic can use either a static threshold (e.g., flag profit below 100K) or a dynamic reference metric (e.g., flag Profit when Margin is below 20%). You can select the reference column from either Viz Config (calculated fields in the current visualization) or from underlying Business View columns—giving you complete control over how comparisons are made.
Formatting based on dates You can now include date fields (Year, Quarter, Month) in your conditional logic. For example, highlight cells where Revenue in 2021 is lower than in 2020. This allows intuitive side-by-side comparisons and makes it easier to visualize time-based trends like WoW, MoM, or YoY directly within Pivot Tables.
These enhancements make it significantly easier to surface critical insights at a glance, without the need for pre-aggregated data or extra calculated columns.

All conditional formatting scenarios work on both old and new pivot tables AND regular tables. Formatting dimensions only works on the old pivot table, not the new one. Users can switch between old and new pivot tables using the "Use Advanced Pivot" toggle in configuration.
Moving percentage & absolute change in Vizpad table calculations
You can now apply Moving Percentage Change and Moving Absolute Change directly in Vizpad table-level calculations for any numerical measure.
This is especially useful for time-series use cases like:
13-week rolling revenue trends (Compare metrics over a rolling 13-week window against the immediately preceding 13-week window to analyze short-term trends and fluctuations in performance over time.)
Year-over-Year growth by week or month (Compare W1 of 2024 vs. W1 of 2025 by partitioning on week and sorting by year.)
Month-over-Month comparisons with custom periods
For example, you can now calculate % change in profit for January 2025 versus January 2024, or view how revenue changed over the last 13 weeks versus the previous 13.

Moving Percentage/Absolute Change calculations only include a "Moving window (years)" field and do not display "Previous years" and "Next years" fields since percentage/absolute change calculations compare two specific time periods (current vs previous) to measure growth rates for period-over-period analysis.
Our fallback logic ensures that if data from the previous window is missing, Tellius intelligently substitutes a valid window from an earlier time period. For example, if you want to see your company's 3-year average profit ending in 2024, ideally you use 2022, 2023, 2024 data. If 2023 is missing, Tellius automatically uses 2021, 2022, 2024 data instead, giving you meaningful results even when your data has gaps.
Lightweight integration of Kaiya into Assistant
In Tellius 5.6, we’ve introduced a compact, embedded version of Kaiya—our AI-powered analytics assistant (with agents)—designed to fit seamlessly within the Tellius Assistant interface. This lightweight deployment includes a collapsible chat bubble that expands into a minimal, embedded chat window, enabling users to interact with Kaiya without leaving their current workflow. Users can ask questions and receive guided responses directly inside the Assistant interface, with optimized performance and minimal screen clutter.
This release is especially relevant if you’re looking for scalable, low-friction NLQ (Natural Language Query) experiences. The embedded Kaiya retains support for quick charts, guided prompts, and smart redirect links to the full Kaiya app for more advanced exploration.

Writeback now supported for Oracle
You can now write back curated datasets from Tellius directly into Oracle databases—joining the list of supported destinations like Snowflake, Redshift, MySQL, and HDFS. This enables teams to operationalize prepared or enriched data within the Oracle ecosystem without switching tools. From the Writeback panel under Data → Prepare → Data section, you can export a dataset to Oracle by choosing a target schema/table, selecting columns to include, and specifying whether to append to or overwrite an existing table.
This feature enables sending recurring workflows directly to Oracle on a regular schedule—no need for a separate ETL process. Writeback honors schema-level permissions, so ensure the target Oracle database allows write access.

Vizpad enhancements
You can now select preceding quarter-to-date (QTD) and year-to-date (YTD) periods directly when comparing timeframes. Previously, choosing "month-to-date" (MTD) provided only the "preceding period" option, limiting comparisons. Now, for instance, if you select May 1-4 as your primary period, you can directly select the preceding period as either April 1-4 or April 27-30, as per your analysis needs.

We've introduced flexible formatting for percentage values in 100% stacked bar charts. Previously, formatting options only applied to the base metric, leaving percentage values fixed. Now, you can individually format both base metrics and their percentage representations (e.g., setting percentage decimals), ensuring precise and clear data presentation tailored to your reporting standards.

In Vizpads, users can now set any saved custom view as the default, so each Vizpad opens exactly how they want it every time. To improve clarity around view modifications, a new Save prompt automatically detects unsaved changes and notifies the user before they navigate away or switch views. These updates reduces accidental overwrites or missed edits.

Sorting and formatting preferences applied in the Vizpad view mode are now consistently reflected in exported files (PPT and CSV). Previously, certain settings (e.g., suffix removal or sorting preferences) were not preserved upon export. This consistency ensures your exported reports accurately reflect your on-screen configurations.
The "Apply" button in single-select (radio button) filters has been removed to streamline interaction. Single-select filters now automatically apply selections immediately upon clicking, removing unnecessary clicks and speeding up your workflow.

Last updated
Was this helpful?