Delete

Introduction

Delete steps remove existing records, so they deserve a clearer mental model than just pressing a button. This tour explains where Delete fits in the CRUD workflow, which conditions you should verify before removing data, and how to avoid turning a useful cleanup action into an accidental destructive change.

Confirm intent + restrict access

Refresh data after delete

Delete Records

Use the Database Delete step to remove rows from a table. Deleting is irreversible, so confirm intent and restrict access.

Delete with a strict condition

Restrict by auth/session

Use Confirmations

When deleting from a UI, add a confirmation prompt and show feedback after deletion.

Confirm user intent

Show success/error feedback

Refresh Data

After deletion, refresh the data source (e.g. re-run the Server Connect component) so the UI reflects the change.

Re-run data source after delete

Update UI lists/details

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