# Event tables

To get to the Event Tables, go from *General Configuration* to *Event tables*:

<div><figure><img src="/files/K3dMR4hu6PEdF5ftE4nI" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="/files/6b8FemX1izY17JyK9WUR" alt="" width="375"><figcaption><p>Event Tables</p></figcaption></figure></div>

## Add EventTable

From the *Event tables* view, click on the  *Add EventTableBundle* button situated at the top right corner:

<figure><img src="/files/6b8FemX1izY17JyK9WUR" alt="" width="375"><figcaption></figcaption></figure>

The editor for the new EventTableBundle will show up. Fill in the required information:

<div><figure><img src="/files/suxjsWPIbVy2bTDAICyR" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="/files/vG2b7Bfd1IR6LwRAhuHW" alt="" width="375"><figcaption></figcaption></figure></div>

* ***coolname*** - (required) the name of the Event Table *(ex: Event Table Testing*)
* ***JSON*** - (required). The code is the Event Table! &#x20;

If the code written in JSON is correct, the EvenTableBundle could be saved. If there is a problem in the code - the 'red X' will show on the left side of the line that should be correct:

<figure><img src="/files/nCRGR5ZdVNh5DQqQaCYP" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
*NOTE: To learn how to write the JSON code, go to the* [*JSON structure*](/user-manual/designer-user-manual/general-conf/configuration/event-tables/tables/json-structure.md)*. All the elements are explained there, along with an example.*
{% endhint %}

* ***trashed*** - disregard/leave empty. This is to be filled in by ADMIN.
* ***plugin*** - (required). This is to be filled in by ADMIN. (ex. *fw\.demo*)&#x20;
* ***componentXid***  - (required). This is to be filled in by ADMIN. (ex. *testing\_table*)

Once all the errors from JSON are corrected,  and the both *plugin* and *componentXid* are set, the new buttons shows up and the possibility to save the EvenTable appears.&#x20;

<figure><img src="/files/fe9q4G0xOLWM1VXjNXTV" alt="" width="375"><figcaption></figcaption></figure>

When the EventTableBundle is created - you know it:&#x20;

<figure><img src="/files/Qd3qqN110f5gBEyN4lgg" alt="" width="242"><figcaption></figcaption></figure>

## Visualize EventTable

EventTable is accessible through the URL. From the URL of the basic page, add the '*/table/pluginName-componentXidName?count=50\&live=false*' . We limit the number of events to 50 (*count=50*) and the real time display to false (*live=false*). In our example it could be: *<https://yourPage.flightwatching.com/wilco/#/table/fw.demo-testing\\_table?count=50\\&live=false>*

<figure><img src="/files/aLgOdt4KFWhybVQsBrVv" alt="" width="375"><figcaption><p>EventTable</p></figcaption></figure>

## Edit EvenTable

In order to edit any EventTable, go from *General Configuration* to *Event Tables* and choose the table to edit. Click on table name to enter to its editor:

<figure><img src="/files/72lmKfPWJ5wBWZpBcDNO" alt="" width="375"><figcaption></figcaption></figure>

All the fields could be modified.

{% hint style="warning" %}
*Note: Pay attention to the plugin and componentXid. Those values are the references that are used to* [*visualize the table.* ](#visualize-eventtable)
{% endhint %}

In order to modify the JSON, you could either work directly on the editor, or copy the content to the application or notepad to modify it. See how to do it [here](/user-manual/designer-user-manual/general-conf/configuration/event-tables/tables.md).

## Delete EventTable

In order to proceed with the deletion,  click on the *Delete Doc* button situated on the top right side of the window.


---

# 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.flightwatching.com/user-manual/designer-user-manual/general-conf/configuration/event-tables.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.