> For the complete documentation index, see [llms.txt](https://doc.sysdevmobile.com/kalipso5/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-database/kill-table.md).

# Kill Table

Deletes one or more records from the specified Database Table, allowing you to choose between Synchronized or Not Synchronized records.

Action available for the following operating systems:

![](/files/-MAlQBZuuTnc6hyzKSVQ)

### Parameters

Marked as

* **All -** **Where** will be applied to all of the records of the **Table**.
* **Synchronized -** **Where** will be applied only to the records who are already synchronized with the server.
* **Not Synchronized -** **Where** will be applied only to the records who haven't been synchronized with the server.<br>
* **Table** - Offline Database Table.
* **Where** *\<Kalipso Filter> or \<string> -* Condition to specify which records should be deleted. Check **Expressions** chapter for more information about **Kalipso Filter** and **String** expressions.

### Usage

Consider the following database table:

| **Products** |            |           |                                              |
| ------------ | ---------- | --------- | -------------------------------------------- |
| **Code**     | **Name**   | **Stock** | **Status**                                   |
| 1            | Coca Cola  | 100       | **Synchronized**                             |
| 2            | Pepsi Cola | 200       | <p><strong>Not Synchronized</strong><br></p> |
| 3            | Pork Chops | 300       | **Not Synchronized**                         |

**Example 1**

|           |                                   |
| --------- | --------------------------------- |
| Marked as | All                               |
| Table     | Products                          |
|           |                                   |
| Where     | FIELD(Products,Name) LIKE "%Cola" |

**Result:**

| **Code** | **Name**   | **Stock** |
| -------- | ---------- | --------- |
| 3        | Pork Chops | 300       |

**Example 2**

|           |                                   |
| --------- | --------------------------------- |
| Marked as | Synchronized                      |
| Table     | Products                          |
|           |                                   |
| Where     | FIELD(Products,Name) LIKE "%Cola" |

**Result:**

| **Code** | **Name**   | **Stock** |
| -------- | ---------- | --------- |
| 2        | Pepsi Cola | 200       |
| 3        | Pork Chops | 300       |

{% hint style="info" %}
This function only works with offline database tables.
{% endhint %}

{% hint style="info" %}
When you specify more than one condition in **Where** parameter, the operator used between the conditions is "**AND**" or "**OR**".
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-database/kill-table.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.