# Local Table

Local Table is a memory table designed to cache data from external sources in a self-defined tabular format locally. Management of data within the local table is performed through related actions (logic blocks). The following fields sets the configuration of a local table.

## Name

* **Description**: The user-defined identifier for the specific configuration or table instance.
* **Type**: Text (string)
* **Example**: "UserDataLocalTable"

## Autoload

* **Description**: A boolean value (true/false) that indicates whether data from this table should be loaded automatically onto the datalist component. This setting applies only once, during the initial loading of the datalist on page load event. Note that the table must be linked to a datalist component within a page before enabling this option.
* **Type**: Boolean
* **Example**: true

## Autoclear

* **Description**: A boolean value (true/false) that indicates whether this table should be automatically cleared of data on page load event. This setting applies only once, during the initial loading of the datalist on page load event. Note that the table must be linked to a datalist component within a page before enabling this option.
* **Type**: Boolean
* **Example**: false

## Uniquekey

* **Description**: A boolean value (true/false) that indicates whether a unique key constraint should be applied to the data in this table. When set to true, a unique identifier is generated for each record, ensuring data integrity and uniqueness. The unique identifier for each record can be accessed by the generated "\_id" column in the table.
* **Type**: Boolean
* **Example**: true

## Fields

* **Description**: Defines the fields or attributes present in the Local Table along with their types. This is represented as a dictionary (object) where each key is a field name and its value is an object containing the field type.
* **Type**: Object
* **Example**: `{"user_id": {"tp": "text"}, "username": {"tp": "text"}, "email": {"tp": "text"}, "age": {"tp": "integer"}}`


---

# Agent Instructions: 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:

```
GET https://docs.emobiq.com/emobiq-client/008-services/001-services-reference/local-table.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.