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.
This example creates a field called average_value by averaging the value dimension, and maintaining a precision of 10 digits following the decimal point:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[],null,["# precision\n\n\u003cbr /\u003e\n\nUsage\n-----\n\n```\nview: view_name {\n measure: field_name {\n precision: 10 \n }\n}\n```\n\nDefinition\n----------\n\nIn Explores where fanout joins could cause incorrect results for aggregate functions, Looker applies [symmetric aggregate](/looker/docs/2512/best-practices/understanding-symmetric-aggregates) logic to return correct calculations.\n\nFor aggregate fields where [symmetric aggregate](/looker/docs/2512/reference/param-explore-symmetric-aggregates) 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:\n\n- Set the value of `precision` to `7` or higher if you need more digits after the decimal point for your calculations.\n\n- Set the value of `precision` to `5` or lower when working with very large numbers, to avoid overflowing the decimal limit on your database.\n\nFor more information about symmetric aggregates, see the [Understanding symmetric aggregates](/looker/docs/2512/best-practices/understanding-symmetric-aggregates) Best Practices page.\n| **Note:** The `precision` parameter applies only for calculations with Looker's symmetric aggregate functionality. If you want to simply change the decimal precision of field values in the data table and visualization, use the [value_format](/looker/docs/2512/reference/param-field-value-format) parameter instead.\n\nExamples\n--------\n\nThis example creates a field called `average_value` by averaging the `value` dimension, and maintaining a precision of 10 digits following the decimal point: \n\n measure: average_value {\n type: average\n precision: 10\n sql: ${value} ;;\n }"]]