> For the complete documentation index, see [llms.txt](https://help.pickzen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickzen.com/guides/nocode/builder/tables/cell-types.md).

# Cell types

A cell can be of any of the following types:

### Boolean

Values of *true* or *false*:

![](/files/-MA_j5bzCx0wcsYX7xIm)

![](/files/-MA_j1TmP31ObIwN8bNt)

### Number

Any integer or float

![](/files/-MA_imcolPWlPCoSGg7Y)

### String

Anything else that is not a Boolean or a String:

![](/files/-MA_jNIcXDDXYBP9lvtK)

The No-Code engine tries always to disambiguate the expression entered. However, sometimes, a string can contain certain characters that can generate interpretation conflicts. For example, if in an **executable table** we write:

![](/files/-MA_kQ_i2Xk-kmVV946S)

The output will be:

```
sku1: Undeclared {id: "SKU123"}
sku2: -123
```

We can see that both sku1, and sku2 have unexpected values. In the first case, sku1 is assigned to an undeclared variable SKU123 instead of the string SKU123. In the second case, sku2 is assigned the value -123, because the engine interprets that SKU is a variable with value 0.

In order to disambiguate in these situations, we only have to enclose the string in simple quotes:

![](/files/-MA_lJHXPNoFppr5OyJc)

In this case, the output will be:

```
sku1: 'SKU123'
sku2: 'SKU-123'
```

{% hint style="info" %}
Note that ambiguities can only occur in executable tables, where cells are interpreted. In data tables, we won't have this kind of problem.
{% endhint %}

### Group

A group is a key-value object. 

### List

A list is a collection of elements.


---

# 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://help.pickzen.com/guides/nocode/builder/tables/cell-types.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.