Skip to main content

They say “All roads lead to Rome”, we say “But some are faster than others”.

There are many ways to get on with Holistics 4.0, and we want to bring you on the quickest path. In October, we introduced an upgraded flow to help your onboarding experience with 4.0 as effortlessly as possible. You’ll be guided throughout the whole process - from your first data source connection to your first datasets, and to your first report.

You can just follow the flow, click, clack, sit back, and relax.


On Oct 12, we released Lazy-rendering Widgets, as part of our effort to further improve Holistics dashboard performance.

Lazy-rendering make sures that all widgets are executed when the dashboard is opened, but only those currently in the viewport are actually rendered. As a result, the initial loading of each dashboard becomes significantly faster and more responsive.

In contrast, without lazy-rendering, every widget would execute and render as soon as the dashboards are opened, resulting in an accumulation of widget renderings and causing the browser to become sluggish.

And because actions speak louder than words, let's go through a quick demo here. :)

In the below demo videos, we're using a dashboard with 20 Pivot Tables.

Before Lazy Rendering

It took nearly 10 seconds for the Dashboard to be responsive. This gets worse as the total number of widgets in the Dashboard goes up.

After Lazy Rendering

It took 1-2 seconds for the Dashboard to be responsive!

More performance optimizations and features are on the way! If you have any questions or feedback for this functionality, feel free to share it here.


In October, we're making some great updates to our Dashboards As Code, making it easier to build reports using code and have fine-grained control over viz, layout, content, and reporting architecture.

We started testing this internally this month and can't wait to share with you a short demo - but before we get to it, here's a peek at how our data team has been using it:

Triet Le (Analytics Engineer): “I can code the entire dashboard into a narrative that people want to read and engage with.”

Huong Le (Data Analyst): “It becomes a lot easier to reuse a dashboard. I just need to clone it, change filters, change dimensions, and re-format it on the fly.”

With this feature, analysts will soon be able to adopt software best practices in your dashboard development. Through codification, you can have full control over the content and design of your dashboards, easily revert changes, make bulk updates, and have customized and reusable visualizations everywhere.

If you’re as excited as we are, stay tuned. We’re running as fast as we can to get this on your hands! :) Without further ado, here’s the new demo.

How do you see this feature being useful to your team? If you have any feedback or suggestions for us, please share them here. We’re all ears.

P/s: We had a lot of fun testing this feature. Our team was even able to whip up a Pokedex dashboard in just a few minutes.


“What is this dataset about? How should I use it? Who can I contact to learn more about using this dataset?”

Sounds familiar? Business users need to really understand a dataset to self-serve effectively. This is why how you present a dataset is as important as how you design it.

From now on, you can write markdowns to add Descriptions to your dataset, making it easier for business users to navigate and explore the data you’ve prepared.

Have any feedback or questions? Share it here with us.


We believe that data should inform action and the faster you can act, the better. This is exactly why we are working on Webhook for Data Alert - a major upgrade to Holistics Delivery capability.

With this, you can quickly set up automated workflows for critical internal communication, like:

  • Sending alert messages to the Purchasing team’s Telegram when inventory runs low, or
  • Buzzing the marketing team on Slack when ad spending goes over the limit.

We value your feedback, so please don't hesitate to share your thoughts and suggestions.


Our PoP has been a hit with our users because it takes just 03 clicks to uncover data trends over time - but things got a lot more laborious when you want to compare:

  • Sales numbers for 'Black Friday' season this year vs. the previous year, or
  • The number of registrations for an upcoming webinar vs. a previous webinar from six months ago.

The problem? Two arbitrary time periods. Different start dates. Different end dates.

🥁🥁 Glad to share that this is a problem of the past! With our newly released Custom Period, you can easily select any date range for Period-over-Period comparison.

If you have any feedback for us, we're all ears.


What makes a good coding IDE? Among other things, it helps you spend as little time on troubleshooting as possible.

With Reporting Validation, you take the guesswork out of your modeling workflow. Holistics IDE now tells you exactly which reporting items are broken due to Modeling changes - before you roll out these changes and lets you patch up all those broken reporting items swiftly and en masse.

P/s: We’re always excited to ship new features, but we’re way more excited when we get to build things that you all have asked us for. Take this new feature for a spin, and keep the feedback coming.


We have released a new option in Single-select List filter settings, where you can allow your dashboard viewers to leave the value field empty.

With this feature active, an empty value can be used without the need to apply the filter. We believe this change offers more flexibility and command over your filtering choices

We value your feedback, so please don't hesitate to share your thoughts and suggestions with us.


Query Timeout helps you abort any query that exceeds your timeout limit and takes too much time and resources.

However, previously in Holistics, the Query Timeout setting was only available for Postgres, Redshift, and MySQL databases. Understanding the importance of resource optimization - especially in our current economic climate - we’ve gradually expanded our support for Query Timeout in most SQL databases - making it also available for BigQuery, Snowflake, Microsoft SQL Server, ClickHouse, and AWS Athena.

Learn more here.

If you have any feedback for us, we're all ears.