# Subform

**Category**: Field

**Version**: 1.0

**Last Updated**: March 20, 2026

**Author**: Any2Info

***

### Description

The **Subform** field allows using forms within a form. Nested potentially endlessly deep. Saved Form Messages are displayed in an overview in the **Subform** field.

***

### General Properties

The **Subform** field inherits general Field Properties such as ‘Font size’, ‘Font color’ and ‘Icon color’. The **Subform** field also has some special properties.

***

### Special Properties

Properties will be listed for each foldable sub-section.

#### Properties - Definition

| Name            | Value             | Explanation                                                                                                                                   |
| --------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Form definition | A form definition | The form definition that can be edited, added to or deleted from                                                                              |
| Immediate save  | Boolean           | Whether or not the subform message is saved to the server instantly. By default, subform messages are only saved when the root form is saved. |

#### Properties - Value linking

| Name            | Value   | Explanation                                                                                                          |
| --------------- | ------- | -------------------------------------------------------------------------------------------------------------------- |
| Links           | Custom  | Allows fields on the current form and the sub form to have linked values. More on this in the **Examples** section.  |
| Update existing | Boolean | Whether or not the current form and already filled subforms have to be re-evaluated when an existing form is opened. |

#### Properties - Navigation

| Name             | Value   | Explanation                                                                                   |
| ---------------- | ------- | --------------------------------------------------------------------------------------------- |
| Navigation       | Boolean | Allow subform navigation between subform messages, without having to go back to the root form |
| Background color | Color   | Sets the background color for the header containing the navigation options                    |
| Font color       | Color   | Sets the font color for the header texts containing the navigation options                    |

#### Styling - Appearance

| Name        | Value   | Explanation                                                                           |
| ----------- | ------- | ------------------------------------------------------------------------------------- |
| Icon hidden | Boolean | Hides the “+” icon, functionally making it so users cannot directly add new subforms. |

***

### Form Overview

The form overview styling in the **Subform** field copies it 1 to 1 from the **Subform** itself.

Options such as “Inline editing” are therefor also supported in the Overview.

***

### Value Linking

Value linking is a relatively straight forward way to take Field values from the root Form to a new Subform, or an existing one if the “Update existing” property is checked.

When configuring Value Links the following popup will be used:

<div align="left"><figure><img src="/files/PQaD57BTyrphOiiISGNx" alt=""><figcaption></figcaption></figure></div>

On the left are the bindable source objects of the Root Form. On the right are the bindable target objects of the Subform. Types are only usuable on the same types between Root and Target. Meaning that MessageID (a number) may only be bound to the “numNumEditor1” field, as this is also a Number based field.

<div align="left"><figure><img src="/files/QVMk8PdEz1X9ZnVEVWsf" alt=""><figcaption></figcaption></figure></div>

When a Source and Target binding are selected, you can confirm the binding by clicking on the center icon.

The selected binding will be added to the Binding box at the top of the popup.

<div align="left"><figure><img src="/files/2ppvezVXpvAvca1MCQYA" alt=""><figcaption></figcaption></figure></div>

### Examples

A default **Subform** field will look as follows:

<figure><img src="/files/6BkZwozF4Ni5JeJyNmRv" alt=""><figcaption></figcaption></figure>

The plus icon allows users to create new Form Messages for the Subform. If the “Icon hidden” property is disabled, this icon will not be shown.

#### Value Linking

In the above screenshot of the default **Subform** field there is also a **Textbox** field. This **Textbox** is used in **Value Linking**, based on the setup shown in [Value Linking](https://www.notion.so/Value-Linking-3293b76aed01805eb595eee4b3c5d424?pvs=21). Meaning that if it filled with a value, such as “Any2Info” that the **Subform** will also have its **Textbox** fields value set to “Any2Info”. As can be seen in the below screenshot.

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

If the “Update existing” property is enabled previously saved Messages will be re-evaluated with the new Value.

#### Form Overview

As previously stated, the Form Overview is copied 1 to 1 based on the Form Overview of the Subforms Form Definition. The screenshot below is an example of this.

<div align="left"><figure><img src="/files/wOhGxr1UzKuEqbVz4RfM" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/9UNiArHRCcmVGMTqLpwF" alt=""><figcaption></figcaption></figure></div>

#### Navigation

If **Navigation** is enabled and the user is currently viewing a Subform Message the total amount of Subform Messages will be displayed together with arrows used to navigate to the next or previous messages in that Subform.

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

***

### Changelog

| **Version** | **Date**       | **Change**                       |
| ----------- | -------------- | -------------------------------- |
| 1.0         | March 20, 2026 | Initial document & documentation |


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/forms/fields-toolbox/specials-and-support/subform.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.