Skip to main content

New Table Display cells, multi-statement queries, and dbt

πŸ§‚ Table Display cells with column formatting​

We've revamped our Table Display cells to lay the ground work for some new features that are going to make working will tabular data so much easier! You'll notice that now you can customize the format of your numerical data β€” so go on and set the decimal precision, add a currency, or talk percentages! More on tables soon to come...

🎢 Multi-statement queries​

We've unlocked the ability to send multiple statements to your database in our SQL cells. Create, drop, insert, and update your tables at will! Add some Jinja to your queries and you'll take your database spell casting skills to the next level.

πŸ”’ Single Value cells​

Make a statement about the metrics that matter with our new Single value cells (aka Big Ass Numbersβ„’). Call out the top-level results of your projects in big ole fonts and contextualize them with comparisons to related data.

πŸ’œ dbt 🀝 Hex​

Quickly get the context you need on your datasets, without switching tools. Our dbt integration pulls metadata from dbt about freshness and recent tests directly into the schema browser.

Want to know more about our dbt integration? Read the blog or get the docs.

✨ Cell formatting​

Don't spend time nit-picking over the formatting of your code, just auto format cells with a quick keyboard shortcut, esc+fs!

Bugs squashed​

  • We've added several packages to our default set, including rtree, gspread-pandas, googlemaps, google-auth-httplib2, and tfcausalimpact
  • Command-mode for Input parameter cells was previously not available via the esc key, which has since been resolved.
  • Multiselect Input parameter lists no longer return to the top of the list after making a selection.
  • Keyboard shortcut to switch between views have been updated to avoid conflicts with some international keyboards.
  • A bug which prevented email notifications for comments left on a project has been resolved.
  • Renaming output dataframes of SQL cells was not occurring in place but is now behaving as expected.