DynamoOps
Data

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.

Insert Item

Click ➕ Insert Item in the toolbar. The New Item dialog opens in JSON mode by default, pre-filled with the table’s key attributes so you cannot forget them. The required keys are listed under the editor.

New Item in JSON mode, with the required keys listed above the editor.
Pre-filled editor for a table with userId (PK) and createdAt (SK)
{
  "userId": "",
  "createdAt": ""
}
  1. Write the document

    Plain JSON only. Strings, numbers, booleans, null, arrays and objects map to S, N, BOOL, NULL, L and M.

  2. Click Save Item

    DynamoOps validates the JSON and the key attributes, then writes the item with PutItem. The toast “Item created successfully” confirms and the grid refreshes.

Put overwrites
Inserting an item whose key already exists silently replaces the existing item. There is no conditional write in this dialog. Use PartiQL with a condition if you need insert-only semantics.

Item templates

A template turns the New Item dialog into a structured form for a given table: one input per field, with types, defaults and required flags. Teams use templates to make sure every manually inserted record has the attributes the application expects.

A template with typed fields, defaults and required flags. Key fields are locked.

Click 🧩 Template to open the template editor. The button shows a badge with the number of fields and is highlighted when a template exists. When you open it for the first time, the key attributes are pre-seeded, locked to their schema types and cannot be removed.

Field nametextrequired
The attribute name. Rows with a blank name are dropped on save.
Typeselect
S, N, BOOL, NULL, L or M. Binary and set types are not available in templates.
Defaulttext
Pre-fills the form. For BOOL a true/false select; for NULL a fixed null.
Reqcheckbox
Marks the field as required. Empty optional fields are omitted from the item; empty required fields are included with their cast empty value.
⠿drag
Drag to reorder fields; the order is used in the form.
  • + Add field appends a row; ✕ removes one.
  • 💾 Save Template stores the template locally for this table name; 🗑 Remove Template deletes it.
  • Templates are per machine and per table name, so the same template applies to a table of that name in every account.

Form mode

When a template exists, New Item opens in form mode with one input per field. A toggle in the dialog switches to { } JSON and back to 📋 Form; in JSON mode every template field is pre-filled with its default. Values are cast on save according to the field type:

With a template, New Item opens as a structured form.
TypeCast rule
SStored as typed
NConverted with Number(); empty becomes 0
BOOLSelect true or false; anything else is false
NULLAlways null
L / MParsed as JSON; invalid JSON falls back to an empty array or object

Cloning an item

In the JSON view, click 📄 on a record. DynamoOps deep-copies the item and opens it in the item editor with the same key values. Change the key or keys, adjust whatever else differs and click Save Item. Because the save is a PutItem, saving without changing the keys would overwrite the original, so the editor is your chance to make the copy unique.

Cloning is available from the JSON view only. For bulk duplication, export the items, edit the file and import it back.

Related