Skip to main content

In a time-series report, you may want to group data by different time intervals such as Day of Week, Day of Month, Month of Year, Hour of Day, etc.

Previously, you had to write AQL expressions to extract such date parts from dates. Now, our Date Parts feature helps you easily extract these specific types of dates from time dimensions so that you can slice your data under different time lenses.

For more detailed examples, please refer to this document:


For trend lines and reference lines, in addition to the toggle break down by legend, you also have another toggle, merge into one line, which helps visualize a single global line despite the legend.

Although both toggles produce the same result of one single line in the chart, their calculations differ:

  • Turning off “break down by legend”: This calculates the trend line or reference line based on the total values (i.e., not segmented by legend).
  • Turning on “merge into one line”: This calculates the trend line or reference line based on the segmented values.

For more detailed examples, please refer to these documents:


The Validation API allows you to validate your projects outside of Holistics, enabling smooth integration with CI/CD workflows. This feature is particularly useful in scenarios such as:

  • Validating updates before merging a pull request into the master branch by incorporating the Validation API within the CI/CD pipeline.
  • Validating changes immediately after updates are pushed to the master branch.
  • Running validations prior to using the Publish API to ensure a successful publish.

Previously, every measure in your chart was always broken down by legend. But sometimes, you may want to apply legend to only certain measures, for example, visualizing a total value alongside sub-category values within a chart.

Now, with a simple toggle, you can turn off the “break down by legend” for individual measures, giving you more control over your visualizations.

Supported visualizations include line, area, column, bar, and combination charts.

Note: this feature is only available in AQL-enabled datasets.


Another quality-of-life improvement in Holistics—more data presentation options for Line Interpolation. Now, you can customize how your line charts display changes between data points for better clarity.

A good chart is a chart with great visual clarity, and this little feature helps analysts get one step closer to that.


Copying table values just got a lot easier. You can now right-click on any cell or range to quickly copy and paste values.

Plus, you have the option to choose between formatted (WYSIWYG) or raw values, giving you more control over your data. 🎉

Visit our public doc for more details: Data Table | Holistics Docs (4.0)


Following the success of the Hiding Columns feature in Table, we’re excited to announce a new enhancement: you can now hide Row Fields columns in Pivot Tables!

This update gives you even greater flexibility to customize and manage your data views, tailoring them to your specific needs.

For more information, please visit our public doc here: Pivot Table | Holistics Docs (4.0)

Note:

  • Currently, we only support hiding Row Field columns.
  • This is an aesthetics feature, not a security feature. Hiding a column will remove it from the user’s report view and export, but the data is still accessible and not restricted in any way.

You can now temporarily hide columns that aren’t relevant to your task, giving you a cleaner, more focused view of your data.

Even better, you can still sort your tables by these hidden fields, keeping your data organized without cluttering your view.

For more information, please visit our public doc here: Data Table | Holistics Docs (4.0).

Note: This is an aesthetics feature, not a security feature. Hiding a column will remove it from the user’s report view and export, but the data is still accessible and not restricted in any way.


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.

Dynamically pointing Holistics to different data sources

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.
info

For those of you who separate dev and prod environments based on schema instead of the data source, please refer to our release note about dynamic schemas.

Demo

📩 Interested in Trying It Out?

info

We're kicking off a beta and would love for you to be involved! Sign up here if you want to join in.

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