# ServiceNow write check

> Stops an agent trusting a success code from the ServiceNow Table API: check the field exists, write the stored value, read every write back.

Canonical: https://mikereams.com/ai/servicenow-write-check

Skill · Original · Enterprise architecture · updated 2026-11-12. Part of the [AI Library](https://mikereams.com/ai).

What you get: A sent-versus-stored comparison for every write, and a pass or fail on whether each field exists at all.

When to use it: Before a load, an update script or a report against a ServiceNow table, and when a write returned success but nothing changed.

Ask for it like this: "Check that this field exists on the table, then update one record and read it back before the batch."

Limits: It never writes to production unless you ask for that write, and it stops at the first mismatch.

- Written from two posts: five Table API calls that return success and store nothing, and the partition test for a field that is not there.
- Instances differ, so each rule is a test to run on yours. It uses the public Table and Aggregate APIs only.

Files (MIT): [SKILL.md](https://mikereams.com/ai-files/servicenow-write-check/SKILL.md)

Install with the skills CLI, from https://github.com/solventarchitect/skills:

```
npx skills add solventarchitect/skills --skill servicenow-write-check
```

The reasoning: [Five ServiceNow API Calls That Return Success and Store Nothing](https://mikereams.com/writing/servicenow-api-calls-that-return-success-and-store-nothing), [The Field That Isn't There](https://mikereams.com/writing/the-field-that-isnt-there)

Tags: ServiceNow, CMDB, Table API, data quality