# Export to form

**Category:** Web

**Version:** 1.0

**Last updated:** February 2, 2026

**Author:** Any2Info

***

### Description

The **Export To Form** node is used to create or update forms based on incoming rows from a dataflow.

Each incoming row can result in:

* The creation of a new form
* An update of an existing form
* Or the row being ignored

depending on the provided **FormID**, **Reference**, and node configuration.

The node also supports creating and updating **sub-forms**, adding **attachments**, and assigning **users and user groups** to forms.

***

### Configuration Options

| Setting         | Required | Description                                                                       |
| --------------- | -------- | --------------------------------------------------------------------------------- |
| Connection      | Yes      | Select the connection to the platform where the forms are stored.                 |
| Collection      | Yes      | Select the collection that contains the form.                                     |
| Form definition | Yes      | Select the form definition that determines the structure of the form.             |
| Advanced        | No       | Opens a configuration screen where incoming columns can be mapped to form fields. |
| AllowNew        | No       | Allows the creation of new forms.                                                 |
| AllowUpdate     | No       | Allows updating existing forms.                                                   |
| Form template   | No       | ID of an existing (already filled) form that is used as a template for new forms. |

***

### Form Identification

Existing forms are identified using **FormID** or **Reference**.

#### FormID and Reference behavior

| FormID value                    | Result                                                                                    |
| ------------------------------- | ----------------------------------------------------------------------------------------- |
| FormID > 0                      | The existing form with this ID is updated. A new form is never created.                   |
| FormID = 0                      | A new form is always created.                                                             |
| FormID = null / empty / invalid | The row is ignored.                                                                       |
| FormID < 0                      | Rows with the same negative FormID are treated as a single form. One new form is created. |
| Reference                       | Existing form is updated. If the reference does not exist, a new form is created.         |

**Note:**\
Reference values are **case sensitive**.\
If the Reference field is not enabled on the form definition, updating via Reference is not possible.

***

### Attachments

Attachments can be added to a form using the **paperclip icon**.

This opens a mapping screen where:

* A **Base64 column** containing the file content must be selected.
* A **filename column** containing the file name must be selected.

If the attachment is a **ZIP file**, extraction can be enabled.\
When enabled, the ZIP file is unpacked and all files inside the archive are added individually as attachments.

***

### Assigned Users and User Groups

Forms can be assigned to **users** and/or **user groups**.

This can be configured via the **Assignment** dialog:

* Fixed users or user groups can be selected.
* Or an incoming column can be mapped that contains user or group IDs.

Assignments can affect form visibility in the form viewer.

***

### Output

The node adds the following output field:

| Field      | Description                                                          |
| ---------- | -------------------------------------------------------------------- |
| MainFormId | Contains the affected Form ID of the main form (created or updated). |

***

### Tips & Best Practices

* **Sub-forms**\
  When creating or updating sub-forms, always start from the **main form**.\
  Select the main form as the form definition and navigate to the sub-form via the tree structure.
* **Updating existing forms**\
  When updating a form and the **FormID is known**, use this FormID as the **Reference** to ensure the correct form is updated.

***

### Errors & Troubleshooting

**Forms are created but not visible in the web application**

* The *Assign User* field may not be filled in.
* Or the form is assigned, but the web application is filtering on assigned users.

**Error: field is not writable**

* The target field is not writable (for example, a calculated or read-only data field).

***

### Changelog

| Version | Date             | Change                               |
| ------- | ---------------- | ------------------------------------ |
| 1.0     | February 2, 2026 | Initial documentation version added. |


---

# 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/data-studio/data-hubs/toolbox/import-and-export/platform/export-to-form.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.