Looker 5.24 Release Notes


(Carter Moar) #1

Anticipated Deployment Dates

Release Rollout Begins: September 23, 2018
Release Final & Download Available: October 4, 2018

Release Highlights

In addition to general tweaks and enhancements, this release
comes with new and improved features in the following
categories. Read on for more detail.

Preparing for Release

Please take notice of items marked with a :zap: as they indicate changes to existing functionality and may require your attention. For more information see the Legacy Feature Updates and Features by Section below.

Notable Features

Download Merged Results as CSV

Save, download, and share merged content with ease. Merged Results queries that have been saved to dashboards can now be downloaded as CSV files. From email updates to data science workflows, it has never been easier to use and view merged data outside of the Looker application.


Git Management Via API

In an effort to make LookML development more programmatic and easier to automate, it is now possible to set up and manage git branches and connections from the project endpoint in the experimental API 3.1. Navigate to your Looker instance’s interactive API docs for more information.

Features by Section

LookML and Development

  • :alembic: New API endpoints for git management. The experimental API 3.1 now contains the following endpoints: all_git_branches, git_branch, create_git, update_git, find_git_branch, delete_git_branch

Scheduling and Downloading

  • Download Merged Results as CSVs. It is now possible to download Dashboards containing merged results queries as CSVs.


  • BigQuery Standard SQL. Added support for DATETIME and NUMERIC data types.
  • Amazon Athena. Updated the driver to version 2.0.5.

General Tweaks & Bug Fixes

  • Security
    • Fixed a security issue where users could potentially change ownership of other users’ dashboards.
  • Dashboards, Visualizations, and Explore
    • :zap: :alembic: Series layering order is now determined automatically rather than going right to left when “Enhanced Visualizations” is enabled and multiple series types are selected.
    • Fixed a bug where long-running queries prevented dashboards from loading.
    • Fixed a bug where using custom fields on merged results queries hid the “Explore From Here” button.
    • Fixed a bug where some dashboard tiles showed the following error: Unexpected token � in JSON at position 14.
    • :alembic: Continued improvements to Beta “Enhanced Visualizations” and “Enhanced Renderer”
  • Content Management and Discoverability
    • Fixed a bug where embed users could not navigate backward when saving a Look.
    • Fixed a bug where restoring a Dashboard from the Trash did not also restore Looks.
  • Platform and Administration
    • Fixed a bug causing some general instance performance issues for Powered By Looker Instances.
  • Scheduling and Downloading
    • Fixed a bug where dashboards were rendered wrong in emails due to Gmail UI redesign.
    • Fixed a bug where user-specific timezones were not applied to exported query results.
  • LookML and Development
    • Stopped generating superfluous joins for empty filters.
    • :alembic: Continued improvements to “Experimental Custom Fields”
  • Action Hub
    • :zap: Made some small UI changes to the Admin Menu for the Looker Action Hub

(Carter Moar) #2

(Brendan Vaughn) #3

What does this mean? Were they not supported before? We were seeing no issues previously but curious if there’s something we missed

(Carter Moar) #4

Correct, Looker did not properly handle the DATETIME and NUMERIC database types . I suspect you could have handled them in previous releases by casting in the sql parameter of a dimension, but they will now be handled more elegantly.

(Brendan Vaughn) #5

That makes sense - we were always using that parameter. Thanks Carter!