1+++ 2title = "Field overrides" 3keywords = ["grafana", "field options", "documentation", "format fields", "overrides", "override fields"] 4aliases = ["/docs/grafana/latest/panels/field-options/", "/docs/grafana/latest/panels/field-options/configure-specific-fields/"] 5weight = 700 6+++ 7 8# Field overrides 9 10Overrides allow you to change the settings for one or more fields. Field options for overrides are exactly the same as the field options available in a particular visualization. The only difference is that you choose which fields to apply them to. 11 12For example, you could change the number of decimal places shown in all numeric fields or columns by changing the **Decimals** option for **Fields with type** that matches **Numeric**. 13 14## View existing field overrides 15 161. Navigate to the panel you want to edit, click the panel title, and then click **Edit**. 171. In the side pane, click **Overrides**. 18 19Grafana displays a list of field overrides, if any have been created for this panel. 20 21 22 23## Add a field override 24 25You can override as many fields and add as many field options to each override as you want to. 26 271. Navigate to the panel you want to edit, click the panel title, and then click **Edit**. 281. In the side pane, click **Overrides**. 291. Click **Add field override**. 301. Select which fields an override rule will be applied to: 31 - **Fields with name -** Select a field from the list of all available fields. Properties you add to a rule with this selector are only applied to this single field. 32 - **Fields with name matching regex -** Specify fields to override with a regular expression. Properties you add to a rule with this selector are applied to all fields where the field name match the regex. 33 - **Fields with type -** Select fields by type, such as string, numeric, and so on. Properties you add to a rule with this selector are applied to all fields that match the selected type. 34 - **Fields returned by query -** Select all fields returned by a specific query, such as A, B, or C. Properties you add to a rule with this selector are applied to all fields returned by the selected query. 351. Click **Add override property**. 361. Select the field option that you want to apply. 371. Enter options by adding values in the fields. To return options to default values, delete the white text in the fields. 381. Continue to add overrides to this field by clicking **Add override property**, or you can click **Add override** and select a different field to add overrides to. 391. When finished, click **Save** to save all panel edits to the dashboard. 40 41## Edit a field override 42 431. Navigate to the panel you want to edit, click the panel title, and then click **Edit**. 441. In the side pane, click **Overrides**. 451. Locate the override that you want to change. You can: 46 - Edit settings on existing overrides or field selection parameters. 47 - Delete existing override properties by clicking the **X** next to the property. 48 - Add additional override properties by clicking **Add override property**. 49 50## Delete a field override 51 521. Navigate to the panel you want to edit, click the panel title, and then click **Edit**. 531. In the side pane, click **Overrides**. 541. Click the trash can icon next to the override that you want to delete. 55 56## Example use case for field options and overrides 57 58The following examples show how you might use field options and overrides. 59 60## Field option example 61 62Let’s assume that our result set is a data frame that consists of two fields: time and temperature. 63 64| time | temperature | 65| :-----------------: | :---------: | 66| 2020-01-02 03:04:00 | 45.0 | 67| 2020-01-02 03:05:00 | 47.0 | 68| 2020-01-02 03:06:00 | 48.0 | 69 70Each field (column) of this structure can have field options applied that alter the way its values are displayed. This means that you can, for example, set the Unit to Temperature > Celsius, resulting in the following table: 71 72| time | temperature | 73| :-----------------: | :---------: | 74| 2020-01-02 03:04:00 | 45.0 °C | 75| 2020-01-02 03:05:00 | 47.0 °C | 76| 2020-01-02 03:06:00 | 48.0 °C | 77 78While we're at it, the decimal place doesn't add anything to this display. You can change the Decimals from `auto` to zero (`0`), resulting in the following table: 79 80| time | temperature | 81| :-----------------: | :---------: | 82| 2020-01-02 03:04:00 | 45 °C | 83| 2020-01-02 03:05:00 | 47 °C | 84| 2020-01-02 03:06:00 | 48 °C | 85 86## Field override example 87 88Let’s assume that our result set is a data frame that consists of four fields: time, high temp, low temp, and humidity. 89 90| time | high temp | low temp | humidity | 91| ------------------- | --------- | -------- | -------- | 92| 2020-01-02 03:04:00 | 45.0 | 30.0 | 67 | 93| 2020-01-02 03:05:00 | 47.0 | 34.0 | 68 | 94| 2020-01-02 03:06:00 | 48.0 | 31.0 | 68 | 95 96Let's apply the field options from the [field option example](#field-option-example) to apply the Celsius unit and get rid of the decimal place. This results in the following table: 97 98| time | high temp | low temp | humidity | 99| ------------------- | --------- | -------- | -------- | 100| 2020-01-02 03:04:00 | 45 °C | 30 °C | 67 °C | 101| 2020-01-02 03:05:00 | 47 °C | 34 °C | 68 °C | 102| 2020-01-02 03:06:00 | 48 °C | 31 °C | 68 °C | 103 104The temperature fields look good, but the humidity is nonsensical. We can fix this by applying a field option override to the humidity field and change the unit to Misc > percent (0-100). This results in a table that makes a lot more sense: 105 106| time | high temp | low temp | humidity | 107| ------------------- | --------- | -------- | -------- | 108| 2020-01-02 03:04:00 | 45 °C | 30 °C | 67% | 109| 2020-01-02 03:05:00 | 47 °C | 34 °C | 68% | 110| 2020-01-02 03:06:00 | 48 °C | 31 °C | 68% | 111
