> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/hidden-input.md).

# Hidden Input

## Description

You can use HTML inputs to transfer data in your application from a browser to a server. Most of these inputs are user-visible data that the user has entered in the application. However, there are cases where it is useful to have a client-side script post data to the server on the backend of the application. The *hidden\_input* part allows you to do that.

The part receives the data and stores it in the context. The part also reads the context data and sends it to the browser, so the client-side script can read the data as well. **Note:** This part is not available in the form-part menus.

**Node Type:** You create a hidden\_input using a text input form-part node.

**Used With:** This part can be used with all LogicNets frameworks as well as in standalone applications.

## Create the Node

This part is not available to users through a LogicNets menu, and only LogicNets' employees should use it. To add a hidden\_input node, do the following:

1. In a Designer project, add a text input form-part node to your logicnet.
2. View the code for that node.
3. Change the \_name value from "text\_input" to "hidden\_input" and save the change.
4. Click the Form tab and double-click on the element to configure the part.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-0918b12b29d2c2dab9b96576c73c50f7d063084c%2F2492f7a5-6624-4442-921c-de1d7f915b5d.png?alt=media)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2fd118d937bc44d74b6d6a69c78f4fe63a2b2931%2Fcb0a3840-0008-42df-8edb-8efaaaaf9eb6.png?alt=media)

## Editor Fields

The hidden\_input part has the following configuration options:

| Tab   | Field Name  | Description/Use                                                                                                                             | Type/Options | Optional/Mandatory |
| ----- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Basic | Data Object | This is the path to which the data is written and from which the system reads it.                                                           | Data Object  | Mandatory          |
| Basic | Var         | This is the name of the hidden input. This name must be unique on the client page, so the client-side script can find and interact with it. | Text         | Mandatory          |
| Basic | Default     | This is where you can enter a default value the system writes to the context if the browser does not send data.                             | Text         | Optional           |
| Basic | Decimal     | This is the decimal-point character used in the application; for example, a dot (.) or a comma (,).                                         | Text         | Optional           |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/hidden-input.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.