> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/features/tableau-extension/end-user/data-correction.md).

# Data correction

Data Correction changes data that already exists. You select marks in a worksheet, the matching rows appear as an editable table, you correct what is wrong, and you save. The values are written straight back over the originals.

That is the difference with the other modules: Data Correction **overwrites existing data**. Every change is kept in the audit trail, so you can always see who changed what and roll a value back.

## What it is for

* Correcting wrong or missing sensor readings
* Fixing a typo in a dimension that has no source system to fix it in
* Any data quality problem you can only spot in the dashboard

## How you work in it

{% stepper %}
{% step %}

### Select the marks you want to correct

Until you do, the extension shows **Select 1 or more marks to view \<schema> data.** The author can switch this off, in which case all rows are listed straight away.
{% endstep %}

{% step %}

### Edit the cells

The matching rows appear as a table, one column per field. Type over what is wrong. Nothing is written yet — your edits are staged.
{% endstep %}

{% step %}

### Save

**Save** writes every changed row at once, refreshes the datasources and takes you back. **Changes** next to it shows how many rows are waiting, and lets you look them over or undo one first.
{% endstep %}
{% endstepper %}

{% content-ref url="/pages/nyxTtpcVbAvVFwoGKtzH" %}
[Edit records](https://docs.infotopics.com/features/tableau-extension/end-user/data-correction/edit-records.md)
{% endcontent-ref %}

{% content-ref url="/pages/logGZSJy8Rq8KDf12eza" %}
[Add records](https://docs.infotopics.com/features/tableau-extension/end-user/data-correction/add-records.md)
{% endcontent-ref %}

{% content-ref url="/pages/hmyP54UN7xRCwqhMWgBM" %}
[Remove records](https://docs.infotopics.com/features/tableau-extension/end-user/data-correction/remove-records.md)
{% endcontent-ref %}

{% content-ref url="/pages/jg5MXfBHvdYRQPF9hhd0" %}
[Bulk edit mode](https://docs.infotopics.com/features/tableau-extension/end-user/data-correction/bulk-edit-mode.md)
{% endcontent-ref %}

{% content-ref url="/pages/OvDKY2kbGjHOtqM4sqR3" %}
[Calculations](https://docs.infotopics.com/features/tableau-extension/end-user/data-correction/calculations.md)
{% endcontent-ref %}

{% content-ref url="/pages/XiVo4yNdQX6m8CQPvJC7" %}
[Interpolate](https://docs.infotopics.com/features/tableau-extension/end-user/data-correction/interpolate.md)
{% endcontent-ref %}

{% content-ref url="/pages/8bJq1u9uaVqgpA35P7Ga" %}
[Vertical layout](https://docs.infotopics.com/features/tableau-extension/end-user/data-correction/vertical-layout.md)
{% endcontent-ref %}

## Rows you cannot change

A dashboard author can set *allow edit when* rules: conditions on the row's own values, or on the mark it came from, that decide whether the row may be touched. A row that fails them is shown read-only, and since 6.3.3 its **Remove** is hidden too.

The column that identifies the row — the one tying it to the worksheet — is always read-only, in every row.

Data Correction works the same way in a Power BI report, with one difference: Power BI has no "all marks" state. When nothing is cross-filtered, nothing is selected. See [Power BI extension](https://docs.infotopics.com/features/power-bi-extension.md).

## Configuration

These pages assume the schema is already set up. [Management console](https://docs.infotopics.com/features/management-console.md) covers the server side, and [Getting started](https://docs.infotopics.com/features/tableau-extension/getting-started.md) the dashboard side.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/features/tableau-extension/end-user/data-correction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
