> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/dashboards/widgets/table-widget.md).

# Table Widget

## Overview

The Table Widget in Datacake is **only available in global dashboards**. The Table widget displays certain values of multiple devices. You are able to filter for tags or names to only get a group of devices. It is perfect to get an overview about values of a group of devices. It also gives the possibility to set conditions so you see devices which are measuring problematic values.

## Video

You can check out our video about the Table Widget here:

## Setting up the Table Widget

To get started, create a [global dashboard](/dashboards/global-dashboard.md), and add the Table Widget to your dashboard.

<figure><img src="/files/lJYh0Cox1p4KVPKvrPl9" alt=""><figcaption></figcaption></figure>

## Configuration

#### **Devices**

In this section you create a filter of which devices you will list in your table. You can filter by Tags or parts of the device names. While filtering you will see a short list of devices in the preview on the bottom.

#### **Columns**

Here you can add what to display per device. To identify the device, we recommend to start with *Meta* information like the Device Name (linked). Inside of the *Meta* fields you will find elements like the **Online Status** of your device, the **Serial Number**, the **Date last heard from**, **Device Location** (description) and **Metadata** created on the device (if existing, you will find those inside of your Device's configuration section).

<figure><img src="/files/iZdlqIGeLepvpznaKQ3T" alt=""><figcaption></figcaption></figure>

The next columns should be some *Measurements* like values you want to see. Those are the "Fields" created on your device.

#### **Appearance**

You can set some preferences about pagination, default sorting and some colouring. Feel free to adjust things as you like!

#### **Conditional Formatting**

If you have configured something in the columns tab, you are able to set up rules to get a visual difference on some devices/rows. You can set up the condition of that rule as you like. You have the option to activate "Limit to this column", which will only apply the conditional formatting to the specific column to which the condition was applied. For example, if you define a conditional formatting if TEMPERATURE<=5°C, only the device in the column TEMPERATURE will be coloured.

## Example configuration

<figure><img src="/files/Prr9yuPt8EA5trITsSOF" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/tyiooFKmkmMOHSh4YOIM" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/sglBUmy6nDdH1fM95uZs" alt=""><figcaption></figcaption></figure>


---

# 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://docs.datacake.de/dashboards/widgets/table-widget.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.
