> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/reference/working-with-actions/delete-row-action.md).
# Delete Row
The Delete Row step allows you to delete a row in a table by a given condition.
You need to specify the filter condition to find the row to delete, for example:
```javascript
// id = 23
{{ui.table.deletedRow.data.id}}
```
You can also specify *multiple* conditions. In this case, the row will be deleted if all conditions are met.
The condition(s) you specify will be sent to the server and converted to a `DELETE` statement, for example:
```sql
DELETE FROM users WHERE id = 23
```
You can check the action's *Payload* tab to see the actual conditions sent to the server.
{% hint style="danger" %}
Filters with empty values are omitted from the generated `WHERE` clause. This applies to `null`, `undefined`, an empty string, an empty array, and an array containing only empty values.
An empty array used with `IN` does not create a condition that matches zero rows. The filter is removed instead. For example:
```
id IN [] AND status = 'inactive'
```
is evaluated as:
```
status = 'inactive'
```
This can delete unintended rows. If all filters are removed and **Bulk Delete** is enabled, the action can delete every row in the table.
Validate dynamic filter values before running the action. For bulk operations, add a Condition step before the Delete Row step.
{% endhint %}
No rows will be deleted if the conditions aren't met.
## Additional settings
If you need to delete multiple rows, you can select the [Bulk Delete](/reference/working-with-components/table/more-ways-to-use-the-component/select-multiple-rows-in-a-table.md#batch-delete) checkbox in the action's settings.
{% hint style="danger" %}
We recommend being very careful with this setting since it can delete all rows in the table.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uibakery.io/reference/working-with-actions/delete-row-action.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
