precision

Usage

view: view_name {
  measure: field_name {
    precision: 10 
  }
}

Hierarchy View File view Field Type precision

Possible Field Types Measure Default Value 6 Accepts An integer

Definition

In Explores where fanout joins could cause incorrect results for aggregate functions, Looker applies symmetric aggregate logic to return correct calculations.

For aggregate fields where symmetric aggregate logic is applied, by default Looker returns six digits after the decimal point. Use the precision field to change the number of digits after the decimal point:

• Set the value of precision to 7 or higher if you need more digits after the decimal point for your calculations.

• Set the value of precision to 5 or lower when working with very large numbers, to avoid overflowing the decimal limit on your database.

  Important: Performing symmetric aggregation on measures with large numbers greater than 14 digits can cause errors such as value overflow or collision when computing sum when precision is set higher than 5.

For more information about symmetric aggregates, see the Understanding symmetric aggregates Best Practices page.

Note: The precision parameter applies only for calculations with Looker's symmetric aggregate functionality. If you want to change the decimal precision of field values in the data table and visualization, use the value_format parameter instead.

Examples

This example creates a field called average_value by averaging the value dimension, and maintaining a precision of 10 digits following the decimal point:

measure: average_value {
  type: average
  precision: 10
  sql: ${value} ;;
}