Skip to content

Updating visuals

If you see any images containing outdated UI, please bear with us.

We are updating all content as quickly as possible to mirror our new UI.

Return

Adding, editing, and deleting records in tables

Create records, update them, and delete them safely using your tables.

Steps at a glance ​

  1. Create a table from the Tables subtab in Data & API.
  2. Create records from the table UI (for quick testing).
  3. Use your interface workflows to create, update, and delete records for real users.

1) Create a record (for testing) ​

  1. Open the Data & API tab, then open the Tables subtab.
  2. Select a table.
  3. Click Insert, then Insert a row. Fill in the fields, then click Insert.
The Tables subtab of Data and API with the tasks table selected and the Insert menu open on Insert a row

2) Update a record ​

  1. In the table, double-click a cell you want to change.
  2. Update the value.
  3. Press Enter to save.
A name cell of the tasks table in edit mode after a double-click

3) Delete a record ​

  1. Tick the checkbox of the record you want to delete.
  2. Click the delete button that replaces Insert (for example Delete 1 row).
  3. Click Delete to confirm.
A row of the tasks table ticked, with the Delete 1 row button in place of InsertThe Delete 1 row? confirmation window with the Cancel and Delete buttons

When users edit data in your app, do it through workflows so you can validate inputs and keep the UI in sync:

  1. Bind a form to your record.
  2. On submit, call your table's Update Row API Endpoint. WeWeb creates it with the table when Create API endpoints to access or update table data is turned on.
  3. Refresh the list (for example with Table View: Fetch) or update the UI state.
An Add task workflow that calls the Add Row API Endpoint of the tasks table, then refreshes the My tasks view with Table View: Fetch

Common pitfalls ​

Records do not update in the UI ​

  • After updating, refresh the list (or update the local variable/table view the UI is bound to).

Users can delete too much ​

  • Add a confirmation step before delete.
  • Protect sensitive actions with middleware when data must be protected.