> 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.