> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/help-center/metrics/adding-and-editing-metrics/how-do-i-edit-metrics-in-tables.md).

# How do I edit metrics in tables?

Tables are a great way to make quick updates from consolidated views. Metric tables are available both within an individual activity record and within a parent pact or project folder. Tables use dropdown menus that adjust based on the context in which you’re entering data.

### Create a new metric from a table view

To add a metric using the table, you will:

1. Select an activity record. This identifies which record you are linking the metric to.
2. Select a metric from the provided dropdown list. Remember, the list is dependent on where you are in the system. So if you are in a pact, you will be shown the associated **programmatic metrics**. If you are in you portfolio and you are a standard user, you will be show the **organizational** **metrics**.
3. Enter a `planned_value`.

### Edit a metric from a table view

To edit an existing metric in the table:

1. Open the **Metrics** tab.
2. Select the row for the metric you want to update.
3. Enter the `implemented_value` and/or update the `planned_value`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.fielddoc.org/help-center/metrics/adding-and-editing-metrics/how-do-i-edit-metrics-in-tables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.