Can Landing AI add and remove members in a record?
Landing AI's review screen offered no way to add or remove a line item in an extracted invoice. An attempt to change the list drew the message 'Cannot edit in read-only editor', no add control appeared, and the list still held its original three line items afterwards.
1 of 1 test case failed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Add one member and remove oneFailEvidence
On the review screen of the saved extraction of the plant hire invoice, which listed three line items, we tried to remove the site fencing line and add a concrete mixer weekly hire line at 1 × £95.00. Nothing new was sent to the product.
Every line item in the invoice table The saved schema with line_items as an Array of Object with children description, quantity, unit_price and amount
The tool's response has no text to quote: it is what the evidence under Proofs shows.
| ✗ | Expected: The added line item appears in the extracted list, the removed one is gone, and every other line item is left untouched.Found: Neither change reached the list. Editing the site fencing line drew 'Cannot edit in read-only editor', right-clicking it opened only the browser's menu, and the list still held three items. |
It is a Fail, not Not gradable: the review screen is where the test asks for one line item to be added and one removed, and it answered each attempt but offers no control for either; its only row controls are thumbs-up and thumbs-down feedback icons.
No field-level editing either. Values inside a line item cannot be edited on this screen either: an attempt to edit a value inside one drew the same read-only message.
Only the schema can grow. The only editable control in the view is '+ New Field' in the Schema pane, which adds a field to the extraction schema, not a line item to the extracted list.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | Review and Correction → | |
| Scenario | Repair a record → | |
| Tool | Landing AI → |
Global scenario definition → · Global capability definition → · Landing AI product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.