A bit more work to improve performance when filters are left empty.

New controls to truncate columns headers to two lines. Always trying to make sure styling is in full control, and defaults look great.

Now dashboard styling (CSS, fonts, colors, backgrounds) can be stored into themes that can be used on any dashboard. This new UX allows styling directly in the app, and easy management for consistent, custom styles with minimum effort.

New settings for vanity dashboard URLs, making navigation simple and contextual - now it's as easy as dashboard/CorporateDash instead of dashboard/1 or dashboard/lkjdfs (unless you want that!). This also means that you can more easily make updates to an embedded dashboard without requiring an engineer to point from one identifier to another, by instead pointing to a fixed, immutable URL.

Moving queries across workbooks is usually simple, but not when your queries reference other queries - until now. Now you can move queries with XLOOKUPs or queries with filters from other queries to any workbook, and the dependencies come with - no more thinking, all just works.

A first look at our effort to bring all of the Omni goodness to SQL queries as well. Instead of forcing users to wedge calculations or column relabels or sorts into the SQL block, now it's just simple actions on top of the result table. Little bit more work to do here, but coming soon.

More flexibility for your data models - in_query allows for dynamic SQL generation based upon the structure of your query. This opens up all sorts of new use cases for flexible SQL based upon the filters or columns selected.

The finishing touches on our period-over-period implementation now offer dynamic time offsets even with other time fields selected. An easy way to pull up time offsets without impacting the structure of your baseline query.

New functionality that allows for dynamically swapping the database connection from a branch. Easily switch between prod or staging schemas (not just dbt) in the UI - great for testing data models across mirrored databases during migration or other more complex deployment use cases.

Some fresh code for using key-pair authentication with Snowflake - providing an extra layer of security to basic authentication (ie. username and password) when accessing your Snowflake. Wrapping up code review and tests on it, we expect it to be live next week.

Sometimes you need to customize a view for the purpose of a single topic - new labels, new fields, maybe even different field definitions. Now you can. This work opens up a views: argument inside topics, that allow for ad hoc view declaration, extension, or overrides, without impacting the core view files. Enormous flexibility with this feature to customize topics to any use case - now everything is fair game inside the topic specifically.