> 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/primary-keys-in-data-add.md).

# Primary keys in data add

A record written by Data Add is tied to the datapoint you selected. That tie is only as reliable as the key behind it, so it is worth getting right before people start writing.

## Keep the key unique

The column you map between the worksheet and the schema has to identify one datapoint, not several. When you select a mark, check that it really is a single mark: a selection covering two datapoints with the same key writes a record that belongs to both.

Where a key genuinely is not unique, the extension warns you about it in Data Correction — an icon on the row telling you how many database records share that identifier, and that saving will update all of them.

## Keep the key free of nulls

A null in the key column has nothing to match on. The record is written, but it hangs off nothing, and it will not come back when you select the datapoint again. Filter nulls out of the sheet the extension is connected to, or give them a value.

A record that deliberately belongs to no datapoint is a different thing: that is a *global* record, created on purpose from the form, and marked with a globe icon in the overview. See [Add rows](https://docs.infotopics.com/features/tableau-extension/end-user/add-data/add-rows.md).

{% embed url="<https://youtu.be/bNhDAlGlKF0>" %}


---

# 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/primary-keys-in-data-add.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.
