Update

Introduction

Update steps change existing records, so the important question is not only how to edit a row, but how to target the right one safely. In this tour, you will connect the Update step to the broader CRUD workflow, review the fields that usually change, and understand the checks that keep edits predictable.

Update by primary key

Add authorization filtering

Update Records

Use the Database Update step to modify existing rows. Always include a clear condition (typically by primary key) to avoid changing unintended records.

Update with a strict condition

Avoid mass updates

Build the Update Flow

A typical update action is assembled in a small, deliberate sequence so you can validate each part before changing data.

Inputs and lookup

Open or create the API action, define the record id and allowed fields, then load the current row before updating it.

Restricted update

Map only intended columns and keep the WHERE clause restrictive, usually by primary key plus any authorization filter.

Create or open the update action

Define id and allowed update fields

Query the current record first

Apply the update with a strict WHERE clause

Validate and Secure

Validate server-side and restrict updates to authorized users (Security Provider + session-based filtering). Prefer allow-lists (only update intended columns) over passing whole objects directly into an update step.

Validate inputs server-side

Filter by current user/session

Next steps

Return to the Database Operations menu to continue with Queries, Insert, Update, Delete, or Paging.

Go back to Database Operations

Continue with another topic