Looker 6.14 Release Notes

Anticipated Deployment Dates

Release Rollout Begins: June 9, 2019
Release Final & Download Available: June 24, 2019

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.

:jp:Release Notes in Japanese :jp:

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.

Beta and Experimental Labs Features

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


Notable Features

Localization of Number Formatting

Developers have the ability to implement localized number formatting by using a user attribute. Admins also have the ability to override the user attribute setting of the number formatting.

Render Liquid HTML in the description parameter

Developers have the ability to implement Liquid HTML in the description parameter of fields. Learn more.

Example of liquid in the description parameter:


Example of the Liquid rendered in an explore:

Features by Section

Dashboards, Visualizations, and Explore

Platform and Administration

  • Localization of Number Formatting. Ability to implement number formatting by setting the user attribute, number_format of a user to one of the available number formats. The formatting is not respected on the x-axis of some visualizations. Learn more.
  • New user email configuration option: Allows admins to customize the body content via HTML of the welcome email new users receive to activate their Looker account. Learn more.

Dialects

  • :zap: Upgraded Snowflake driver (v3.8.0). Addresses Snowflake OCSP issue found in prior versions of the driver. Learn More.
  • :zap: Upgraded Athena driver (v2.0.7). Allows defining Workgroup=WorkgroupName parameter in the Additional JDBC Parameters field of a database connection in order to utilize AWS Workgroups .

Scheduling and Downloads

  • :zap: Run Schedule as Recipient is out of Labs Beta. This feature is now fully available on all instances.
  • :zap: Easy to Read Email Images is out of Labs Beta. This feature is now fully available on all instances.

General Tweaks and Bug Fixes

Scheduling and Downloads

  • Improved rendering of tables with more than 100 rows.
  • Improved the rendering of inline visualizations in schedules.

Platform and Administration

  • Improved the ability to filter out Looker Employees from the User Activity dashboard under System Activity.
  • Improved the tracking of user and sudo details in events.
  • Addressed an issue where a user could bypass the account lockout by using a capital letter in the email.
7 Likes

@Dawid_Nawrot :wink:

3 Likes

Can you explain this some more, please? The Liquid looks like it’s row-dependent, so how can a column header be affected? What if the column has multiple values of (in the example) orders.status?

I wonder if that’s just not a great example— I imagine it’d be the same limitations as what’s useful in the label: parameter— Things like _in_query, _explore._name,user attributes, yada yada. Stuff like value probably wouldn’t work, since the description has to be rendered before the result set is generated, in the field picker.

Maybe it’d update the result set hover description, but the field picker description doesn’t re-render on run I think, so I’m presuming it’d be limited to those pre-query parameters that I referenced.

But, I’m totally 100% guessing. @anakarina.lance would be the authority :policewoman:t4:!

This feature wouldn’t affect the column header itself. It would affect the description that is displayed when hovering over the column header. The feature itself allows the rendering of liquid in the description parameter of a field. Let me know if you have any further questions!

Can’t wait to test it out! Awesome… I guess you can sleep well now knowing you don’t need a truckload of chocolates!

1 Like

I think this is a great feature. Would it be possible to extend this feature on labels as well apart from description. It will be a great value add for us.

The label parameter supports liquid, but, depending on how you’re using it you may need to check it out in the visualization instead of the data table. There are some neat examples of use here: Interesting Ways to use Liquid in Labels

Great thanks. Let me do some more exploration here. I should have checked the discourse first :). Anyways will look into this a bit more and get back to you for any questions.

1 Like

Where do I enable Transposition? And will this affect DATA panel so that transposed data can be used in bar chart?

@Dawid_Nawrot the transposition is part of the experimental table-next visualization type and can be enabled on the Labs page. Learn more about Labs features here. Since it’s a visualization, it will not affect the data panel; transposing affects how the data is displayed, but isn’t going to change what data is returned by a query.

That said, the data you currently pull for a query ought to be able to generate a bar chart with or without being transposed. If there’s a problem there, you may want to start a separate thread or reach out to support via help.looker.com because I suspect something else might be up.

ohh I see it’s only available if you select Table-beta, which means I won’t be able to use it in column chart, which is what I was waiting for : (

Problem with scheduler and downloading dashboards and looks.
With this upgrade legacy features needs to be turned on, or you can’t schedule any dashboards or download any. But when next upgrade of 6.16 comes in, legacy features will be removed.
I have logged a call with Looker engineers to get this resolved asap (#228401)

@Dawid_Nawrot I recommend you start a dedicated thread discussing what you’re trying to achieve or reach out via help.looker.com. Transposing the data set is not related to how our column charts work (or any of our other charts, actually), so if you’re unable to achieve something right now something else is going on. A dedicated conversation will help you get back on track.

As far as we currently understand the matter, it appears that this could be related to some instance-level configuration issues; it does not appear to be widespread at this time. That said, we do take it seriously and are working to identify what’s going on and how to fix it. If more folks run into it, please reach out via help.looker.com and we’ll work to get you sorted out.

1 Like

Same here.

Upgraded from 6.12 to 6.14.17 (on-premise), visualizations are not being sent while data table or csv / else is working just fine. Almost all labs features are switched off. From Looker support - EMBED-383 ticket is active and with critical status.

Brief update: This is related to the CDN, so switching off the CDN in your Admin panel: https://docs.looker.com/admin-options/settings/general#load_assets_from_cdn will fix visualizations until we can patch your instance with a permanent fix— At which point you should re-enable the CDN to keep things swift.

Well it is related if it’s only available for table visualisation, isn’t it? I thought Transpose would be an option for all types of visualisation as it would happen after data is retrieved but before passing the data to the visualisation engine, but nobody confirmed it yet

Dawid, I would’ve liked to see it implemented the way you’re describing as well. Seems unfortunately that they’ve tied it to the Table-Next viz instead. I agree it’d be better on the data-calling layer (alongside Totals and Subtotals).

1 Like

@Dawid_Nawrot & @bens
As of now, the Table-Next feature is still in Labs Beta development. That being said feedback is always welcome. Please reach out via help.looker.com and our wonderful support team can share this feedback with our Product team.