Looker 6.20 Release Notes

  • 3 September 2019
  • 12 replies
  • 174 views

Anticipated Deployment Dates


Release Rollout Begins: September 8, 2019

Release Final & Download Available: September 19, 2019


All Release Notes

Legacy Features End-of-life Schedule



Please note that comments on this thread are not formally tracked. For help requests and issue reports please open a separate conversation or reach out via the Looker Help Center to start a specific conversation.




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 ⚡ as they indicate changes to existing functionality and may require your attention. For more information, see the Features by Section below.





Beta and Experimental Labs Features


The following new and improved experimental and beta features are marked with a ⚗:






Notable Features


Data Tests


This feature gives users the ability to test data and query correctness. For code quality, it can be a required step for tests to pass before pushing LookML code to production. API endpoints for this feature are also available. Learn more about creating data tests. Learn more about running data tests from the UI. Learn more about running data tests from the API.


53%20PM


Single Value Visualization Improvements


The ability to conditionally format this visualization is now available. Learn more.


Features by Section


Platform and Administration




  • Account lockouts. Login Lockouts admin page enables admins to unlock a user before the lockout period expires. Learn more.


  • Renamed ‘Spaces’ to ‘folders’.

  • Improved the Browse drop-down menu.

    • Simplified the left sidebar found by selecting the Home option from this drop-down menu.




  • Content curation (boards) is no longer in Labs. Boards provide a way for people to curate and surface existing content for initiatives and teams. This feature works in tandem with folders. In addition, LookML dashboards can now be pinned to boards. Learn more in this overview of boards. Learn more about presenting content with boards.




Dashboards, Visualizations, and Explore




  • Table-Next (Beta) improvements.

    • Users can control per-column text formatting such as font color, background color, text styling, and text alignment. Learn more.






LookML and Development




  • IDE folders. Project generator creates folders for models with multiple schemas.

  • New LookML parameter for native derived tables (NDTs), bind_all_filters, takes all filters from the user query and applies them in the NDT subquery. Learn more.


  • Localization. The default_value parameter in LookML dashboards accepts the Liquid _localization. Learn more.


  • ⚡ View-level drill_fields parameter now applicable to all measures by default. drill_fields applied on a per-measure basis will override the view-level set. Learn more.


Dialects




  • Apache Druid.

    • “Druid” is now “Apache Druid”.

    • Upgraded the JDBC driver to version 0.15.

    • Enabled setting additional JDBC parameters through the JDBC connection string. This enables a connection to use the properties mentioned here.




Embedded Analytics




  • New Javascript click events. Now capturing embed iFrame clicks for drilling, Explore from Here, and Open original Look. Learn more.


General Tweaks and Bug Fixes


Platform and Administration



  • Modified when SQL statements are displayed in the logs based on the chosen logging levels.


LookML and Development




  • IDE folders. Fixed an issue where the menu option to Revert Changes on a single file was no longer available.


Dashboards, Visualizations, and Explore




  • ⚗ Fixed several issues in the Table-Next (Beta) chart:

    • The visualization editor intermittently failed to display menu options.

    • The text in subtotals column failed to align.

    • The color picker not displaying a specific color collection when selected.




API



  • Fixed an issue where the API endpoint all_user_attributes failed with a 500 error when given a sort parameter.

  • Updated the response returned when an embed user did not have a user attribute value for a parameterized connection.

  • Fixed an issue that returned a 404 error message when an admin updated a schedule that wasn’t their own via the API.

  • Updated the Looker API Docs to explicitly require the query_id parameter when utilizing the create_look endpoint.


Scheduling and Downloads



  • Fixed an issue which cut off merged results tiles when rendering a PDF of a dashboard with the option single column layout was selected.

  • Fixed an issue that cut off columns from tables when rendering a single-column PDF.


12 replies

Can we have more documentation available for “Data Tests” feature?

Documentation will be available soon!

Great release, super excited.


Is there documentation coming for the new Embedded Javascript click events?

Yes, that documentation will be published soon!

Userlevel 7
Badge +1

2 posts were split to a new topic: Table & Table-Next Conditional formatting not working

Hi Kaushal! We just now published our docs on the data test feature:


For information on creating data tests, see the test parameter documentation page.


For information on running data tests, see the Using Version Control and Deploying documentation page.


Sorry for the delay, hope that helps!

Hi Jonathan! In case you didn’t see already, we’ve updated the docs with the new events in 6.20. Check out these links:



Thanks so much for your patience!

Thank you for information.

Wow, this release is very exciting!

Thank you Erin!

Userlevel 4

Hi Erin! Is documentation available for running data tests via the API? I haven’t been able to find the endpoint in the API docs.


EDIT: Found it in the Project section! Maybe you can add the link to the original post? https://docs.looker.com/reference/api-and-integration/api-reference/v3.1/project#run_lookml_test

Thank you, thank you! I added it to the original post. Good call!

Reply