Data

Editing items

Fix a value by double-clicking a cell, or open the full JSON editor to change any attribute. Learn the exact type rules DynamoOps applies on save.

Two ways to edit

Inline editing changes a single scalar attribute directly in the grid with an UpdateItem call. The item editor opens the whole document as JSON and replaces it with a PutItem. Use inline edits for quick fixes and the editor for structural changes such as adding nested objects or removing attributes.

Inline editing

Inline editor open on the name column — An inline edit in progress. Enter saves, Esc cancels.

Double-click a cell
Any non-key cell with a scalar value becomes an input. Numeric values get a numeric input; booleans show a true / false placeholder. Double-clicking an object or array opens the item editor instead, and key cells refuse inline edits with a hint to use the full editor.
Type the new value
Leave the field unchanged and nothing is sent.
Commit or cancel
↵ commits, Esc cancels, and leaving the field with ⇥ or a click also commits. The cell reads “saving…” until DynamoDB answers, then shows a confirmation toast. On failure the previous value is restored.

The write is an UpdateItem with a SET on that attribute only, so other attributes are untouched even if the row was stale. Inline edits are reported to Cost Analytics but are not recorded in Version History.

Type rules on commit

DynamoOps decides the stored type from the original value’s type and the text you entered.

Original type	You type…	Stored as
Boolean	`true`	true
Boolean	anything else	false
Number	a number	Number
Number	empty	The attribute is removed
Number	non-numeric text	String — the attribute changes type
null	empty	stays null
null	text	String
Missing attribute	text	A new String attribute
Missing attribute	empty	stays missing
String	text (including empty)	String

Numbers larger than 2^53

Values are handled as JavaScript numbers. Integers beyond 2^53 or high-precision decimals can lose precision when displayed or saved. Edit such attributes with PartiQL instead.

The item editor

Open it with ✎ on a row or JSON record, by double-clicking an object or array cell, or from Restore this version in Version History. The dialog is titled Edit Item and shows the full document as editable JSON.

Edit Item dialog with the item JSON — The item editor shows the full document as JSON.

Validation — malformed JSON and missing or empty key attributes are reported inline before anything is sent.
Save Item — snapshots the item as it was before the edit into Version History, then performs a full PutItem. Attributes you removed from the JSON are removed from the stored item.
Keys — changing a key value does not move the item: it creates a new item and leaves the original in place. To re-key an item, create the new one and delete the old. This is exactly how Clone works.
After saving — the toast “Item updated successfully” appears and the grid refreshes from page 1.

Close the editor with Cancel, ✕, a click outside or Esc.

Table and JSON views

Browse results as a sortable, resizable grid or as collapsible JSON documents. Filter loaded items instantly, select rows, copy items and switch between plain and DynamoDB JSON.

Item version history

Every save through the item editor keeps a local snapshot of the previous version. Browse versions, see a field-by-field diff against the current item and restore any of them.

Creating items and templates

Insert items as free-form JSON or through a structured form driven by a per-table template. Clone existing items to create variations in seconds.

PartiQL (SQL) editor

Write SQL-compatible PartiQL with context-aware autocomplete, statement templates built from your table schema, one-click formatting and guarded write statements.