In new LookML, the vast majority of parameters will be your old familiar friends. The new LookML IDE shows you the available parameters so you’ll be able to easily find the parameter you want. You also can learn more about parameters you haven’t used before.
In the process, you may discover some parameters that existed in old LookML but you don’t recognize. In some cases, we hadn’t documented them – but we’re working on it! Only a few parameters are replacements for old LookML parameters.
The rest of this article lists:
These parameters are replaced by new parameters:
sql_case
is replaced by case
& when
map_layer
is replaced by map_layer_name
This parameter has stricter validation:
filter
is no longer valid in a measure – you must use filters
instead, one for each filter you want to specifyThese parameters existed in old LookML but were undocumented:
default_value
fanout_on
filter
field is now documented and field parameters now mention if they can be used by filter
fields.These measure types just have one way to say them now:
avg
or average
but in new LookML you should use average
avg_distinct
or average_distinct
but in new LookML you should use average_distinct
This parameter is no longer needed in new LookML:
fields
is no longer needed – just start defining individual dimension
, measure
, dimension_group
, or filter
parametersThis parameter was replaced:
This parameter is no longer needed in new LookML:
This parameter was replaced by a new parameter in new LookML:
This parameter was replaced by another parameter in old LookML so is not available in new LookML:
These parameters existed in old LookML but were undocumented:
These parameters were replaced in new LookML:
map_layers
is replaced by map_layer
value_formats
is replaced by named_value_format
This parameter has an additional use in new LookML:
includes
is now also used when referring to an object defined in another file. For example, you now add an include
in a view file when extending or referring to a field declared in another view file.These parameters were deprecated in old LookML so are not available in new LookML:
Here’s differences you’ll see but no worries – the IDE helps fill in the punctuation.
Here’s differences you’ll see but no worries – the IDE helps you get it right.
true
or false
– use yes
and no
.For related info, check out these articles:
I’m glad brettg.
And, yes, the converter takes care of these. You can see what the converter did for these situations by looking at the pages for the prior and replacement parameters. The converter was used to create the new LookML code blocks in documentation.
By the way, if you work with LookML dashboards you’ll notice that they still use old LookML. The LookML converter does not affect any LookML dashboards that you have in a project.
Thank you for this helpful articles. It clears a lot of confusions that I have when I compare old LookML with the new one.
Of course, @Hui_Zheng! Thanks for the feedback!