Looker Community

Change in JSON Render Formatting (6.22+)

In Looker 6.22, Looker’s method for rendering values in some JSON formats for sending, scheduling, and downloading has changed. This change applies to deliveries and downloads through the Looker UI and the Looker API.

Pre-Looker 6.22

Looker uses a dimension or measure’s field name as its rendered value when sending, scheduling, or downloading in JSON format from the Looker UI Scheduler and the Looker API. For example:

{"view.field_name":"rendered_value"}

Looker 6.22+

Looker introduces a new JSON format option for sending and scheduling to some destinations. When scheduling and sending from the Looker UI Scheduler, this option appears as JSON – label. When scheduling and sending using the Looker API, this option is json_label.

Other JSON formats will continue to output field names as the rendered value.

Clicking the Download button will now download the data using the json_label format so that the column names shown in the visualization will match the column names in the downloaded data.

If you use the json_label format option, Looker will use a dimension or measure’s label as its rendered value in its JSON output. For example:

{"rendered_label":"rendered_value"}

1 Like