# Change existing cells or records without breaking the sheet

> Change existing cells or records without breaking the sheet: 3 companies fully do it, 7 with a limit, 10 carry the tag. Every listing in Spreadsheets & operational tables with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/spreadsheets.update-in-place/
- Markdown: https://www.anchorterminal.com/niches/spreadsheets.update-in-place/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/spreadsheets.update-in-place/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/spreadsheets.update-in-place/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 3 | 7 | 10 | 11 | 4 |

## What counts as done

Only the targeted cells change, formatting and comments stay, the update is matched by a key so a repeat changes nothing more, and a read right after shows the new values.

How agents ask for it: mark these rows as done; update the price column; fix the typos in this sheet; set the status for this customer

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Airtable (Formagrid Inc (doing business as Airtable))**: PATCH on Update multiple records changes only the fields sent, by record id or by fieldsToMergeOn, so a repeat changes nothing more; fields can be addressed by id.
- **Grist (Grist Labs Inc.)**: PUT /records matches rows by the require fields and updates only the fields given, with onmany and noadd options, so a repeat changes nothing more; PATCH by row id also exists.
- **NocoDB (NocoDB Inc (doing business as NocoDB))**: PATCH /records changes only the fields sent by record id, and /records/upsert matches on a merge key so a repeat changes nothing more; fields can be addressed by id.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Baserow (Baserow B.V.)**: PATCH by row id or batch PATCH changes only the fields sent, addressed by field_{id}. Matching is by row id only, so an agent keyed on a business field reads before every write.
- **Coda (Superhuman Docs) (Superhuman Platform Inc. (parent of Coda Project LLC))**: PUT on a row by id or name changes only the cells sent, and keyColumns upserts match by key. The update is queued (202), so read-after-write needs a mutationStatus poll.
- **Google Sheets API (Google LLC)**: values.update and batchUpdate change only the cells in the given ranges and keep formatting, but updates address A1 ranges, not a key, so the agent reads to find the row before every write.
- **Microsoft Excel (Microsoft Graph workbook API) (Microsoft Corporation)**: PATCH on a range or table row changes only those cells, but rows are addressed by index or address, not a key, and Microsoft warns that concurrent writes to one workbook cause throttling, timeouts and merge conflicts (acc-30).
- **SeaTable (SeaTable GmbH)**: Update Row(s) changes only the columns sent by row_id, and Lock Rows can stop others editing; SQL UPDATE ... WHERE can match on a key column, but no upsert exists, so a key-matched insert-or-update needs a read first.
- **Smartsheet API + MCP (Smartsheet Inc.)**: PUT /sheets/{id}/rows changes only the cells sent, by row id and column id. Rows are matched by id, not a key, and parallel writes to one sheet with one token return error 4004.
- **Teable (Teable AI, Inc.)**: PATCH /table/{id}/record updates only the fields sent by record id with fieldKeyType=id, but there is no key-based match, so the agent reads before every keyed write.

## What stops agents finishing

- parallel writes to one file throttled or merged wrongly (Graph, Smartsheet 4004)
- no key-based upsert, so the agent reads before every write

## Around it

Before: spreadsheets.filter-records. After: spreadsheets.read-table.

## Where this comes from

Weight 11 of 100 in Spreadsheets & operational tables: 4 of 35 accounts: the diff-only push CLI, NocoDB field ids, Teable duplicates on retry, Excel co-editing conflicts

As data: https://www.anchorterminal.com/api/v1/use-cases/spreadsheets.update-in-place.json, or the MCP tool get_use_case with id spreadsheets.update-in-place. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
