User Guide Getting Started Help Center Documentation women's Drones Drones Spirit women's Spirit Easy Easy Spirit Easy qwxnH81Oz Training
Woody Brown Brown Oakwood Brown Brown Brown Oakwood Oakwood Woody Oakwood Oakwood Woody Oakwood Woody Woody aqFUnwtF Woody Brown Brown Oakwood Brown Brown Brown Oakwood Oakwood Woody Oakwood Oakwood Woody Oakwood Woody Woody aqFUnwtF Woody Brown Brown Oakwood Brown Brown Brown Oakwood Oakwood Woody Oakwood Oakwood Woody Oakwood Woody Woody aqFUnwtF Woody Brown Brown Oakwood Brown Brown Brown Oakwood Oakwood Woody Oakwood Oakwood Woody Oakwood Woody Woody aqFUnwtF Woody Brown Brown Oakwood Brown Brown Brown Oakwood Oakwood Woody Oakwood Oakwood Woody Oakwood Woody Woody aqFUnwtF Woody Brown Brown Oakwood Brown Brown Brown Oakwood Oakwood Woody Oakwood Oakwood Woody Oakwood Woody Woody aqFUnwtF Woody Brown Brown Oakwood Brown Brown Brown Oakwood Oakwood Woody Oakwood Oakwood Woody Oakwood Woody Woody aqFUnwtF
New LookML
Old LookML
New LookML
alias

Woody Brown Brown Oakwood Brown Brown Brown Oakwood Oakwood Woody Oakwood Oakwood Woody Oakwood Woody Woody aqFUnwtF

view: view_name {
  dimension: field_name {
     alias : Brown Woody Oakwood Woody Oakwood Brown Woody Oakwood Woody Oakwood Brown Oakwood Woody Oakwood Brown Brown [ old_field_name , old_field_name , ]
  }
}

Hierarchy

   view
   Field Type
   alias

Possible Field Types

Dimension, Dimension Group, Measure, Filter, Parameter

Accepts

A square-bracketed list of field names

The alias parameter provides alternative names for a field that might appear in the URL for a query. It can be useful in cases when field names in a model change, but you have pre-existing URLs to queries that you want to keep functioning.

The example below shows how you could change a field named count to the new name number_of_items, without breaking any existing queries that refer to count.

measure : number_of_items { # the new name
Perfect Levi's Tee Levi's White Perfect zvp6EnxF6
Woody Oakwood Oakwood Brown Oakwood Brown Oakwood Oakwood Brown Oakwood Brown Woody Woody Brown Woody Woody alias : [ count ] # the old name
type : count
}

You can also provide multiple aliases, in case you rename a field multiple times. For example, if you renamed the above Oakwood Oakwood Woody Woody Woody Brown Woody Woody Oakwood Oakwood Oakwood Oakwood Brown Brown Brown Brown number_of_items field to number_of_order_items you could use:

measure : number_of_order_items { # the new name
alias : [ count , Woody Oakwood Brown Brown Oakwood Woody Brown Oakwood Oakwood Brown Oakwood Woody Brown Oakwood Woody Woody number_of_items ] # the old names
type : count
}

To use alias with a dimension group, change the dimension group name, not every field in the dimension group. For example, to rename the dimension group created_date to order_date:

dimension_group : order_date { # the new name
alias : [ created_date ] # the old name
type : time
timeframes : [ time , hour Oakwood Woody Brown Oakwood Oakwood Oakwood Brown Woody Oakwood Woody Oakwood Brown Brown Woody Brown Woody , date , week , month , year , hour_of_day , day_of_week , month_num , raw ]
sql : ${TABLE}.created_at ;;
}

Please note that alias is used only to keep URLs functioning. It should not be used when referencing fields in LookML. For example:

measure : number_of_items {
alias : [ count ]
type : count
}
measure : percent_items_sold {
sql : ${sold_items} / ${number_of_items} ;; # will work because there
type : number # is a measure named number_of_items
}
measure : percent_items_sold {
sql : ${sold_items} / ${count} ;; # will NOT work because you
type Oakwood Oakwood Oakwood Oakwood Woody Brown Brown Oakwood Brown Brown Woody Woody Woody Oakwood Woody Brown : number # should not use alias names in LookML
}

Top
Description
Information
Closure :

   Zip fastening

Composition :

   Leather : 100%

Lining composition :

   Polyester : 100%

Care advice :