LookML modeling best practices let you build maintainable data models that
aggregate metrics accurately and optimize query performance. You can apply
these guidelines to configure join relationships, primary keys, object names,
datagroups, and dimension groups, while adapting each recommendation to your
environment.

## Do this with LookML

- **Do** : Define the [`relationship`](https://docs.cloud.google.com/looker/docs/reference/param-explore-join-relationship) parameter for all joins.

  <br />

  This will ensure that metrics aggregate properly within Looker. By default, Looker will use a `many_to_one` join relationship for any joins in which a relationship is not defined. For additional information on defining the `relationship` parameter correctly, see the Best Practices page on [getting the `relationship` parameter right](https://docs.cloud.google.com/looker/docs/best-practices/how-to-use-the-relationship-parameter-correctly).
- **Do** : Define a [primary key](https://docs.cloud.google.com/looker/docs/reference/param-field-primary-key) within each and every view, including derived tables.

  <br />

  All views, whether they are derived or coming directly from the database, should contain a primary key. This primary key should be a *unique value* to enable Looker to uniquely identify any given record. This primary key can be a single column or a concatenation of columns --- it simply needs to be a unique identifier for the table or derived table.
- **Do** : Name [dimensions](https://docs.cloud.google.com/looker/docs/reference/param-field-dimension), [measures](https://docs.cloud.google.com/looker/docs/reference/param-field-measure), and other LookML objects, using all lowercase letters and underscores for spaces.

  <br />

  The [`label` parameter](https://docs.cloud.google.com/looker/docs/reference/param-field-label) can be used for additional formatting of a name field, and can also be used to customize the appearance of [view names](https://docs.cloud.google.com/looker/docs/reference/param-view-label), [Explore names](https://docs.cloud.google.com/looker/docs/reference/param-explore-label), and [model names](https://docs.cloud.google.com/looker/docs/reference/param-model-label). For example, in the following LookML, the `label` parameter is used to assign the label **Number of Customers** to the `customer_count_distinct` measure.

  ```
        measure: customer_count_distinct {
          label: "Number of Customers"
          type: count_distinct
          sql: ${customer.id} ;;
        }
  ```
- **Do** : Use [datagroups](https://docs.cloud.google.com/looker/docs/reference/param-model-datagroup) to align generation of [persistent derived tables (PDTs)](https://docs.cloud.google.com/looker/docs/caching-and-datagroups) and Explore caching with underlying ETL processes. Datagroups can also be used to trigger deliveries of [dashboards](https://docs.cloud.google.com/looker/docs/scheduling-and-sending-dashboards#schedules_triggered_by_datagroup_updates) or [Looks](https://docs.cloud.google.com/looker/docs/delivering-looks-explores#specifying_the_datagroup_trigger) to ensure that up-to-date data is sent to recipients.

## Don't do this with LookML

- **Don't** : Use the `from` parameter for renaming views within an Explore.

  <br />

  <br />

  Use the [`view_label`](https://docs.cloud.google.com/looker/docs/reference/param-explore-view-label) parameter instead. For more on the difference between `from` and `view_label`, check out the [`from` (for Explores)](https://docs.cloud.google.com/looker/docs/reference/param-explore-from) parameter documentation page. The `from` parameter should primarily be used in the following situations:
  - Polymorphic joins (joining the same table multiple times)
  - [Self-joins](https://docs.cloud.google.com/looker/docs/working-with-joins#joining_a_view_more_than_once) (joining a table to itself)
  - Re-scoping an extended view back to its original view name
- **Don't** : Use the word "date" or "time" in a [dimension group](https://docs.cloud.google.com/looker/docs/reference/param-field-dimension-group) name.

  <br />

  <br />

  Looker appends each timeframe to the end of the dimension group name, which means that a dimension group that is named `created_date` results in fields called, for example, `created_date_date` and `created_date_month`. Simply use `created` as the dimension group name, because this results in fields that are named, for example, `created_date` and `created_month`.
- **Don't** : Use formatted timestamps within joins.

  <br />

  <br />

  Instead, use the [raw timeframe](https://docs.cloud.google.com/looker/docs/reference/param-field-dimension-group#timeframes) option for joining on any date or time fields. This will avoid the inclusion of casting and timezone conversion in join predicates.