# Set Input Value in Data Design

{% hint style="info" %}
**Block Information**

Available in: Page Flow

Toolbox Category: Dynamic Input

Block Type: [Regular](/app-editor/page-flow/block-anatomy.md#regular-block)
{% endhint %}

**`Set Input Value in Data Design`** is a [regular block](/app-editor/page-flow/block-anatomy.md#regular-block) that allows you to set the value of [Input](/app-editor/page-editor/built-in-elements/input.md), [Dropdown](/app-editor/page-editor/built-in-elements/dropdown.md) and [Multi-line](/app-editor/page-editor/built-in-elements/multi-line.md) elements that were generated using the [Content from Data Design](/app-editor/page-flow/toolbox-blocks/content-from-data-design.md) block and dynamically added to the page or form.

<div align="left"><figure><img src="/files/n5bbFdcxj0o2Pm5uxkcj" alt="" width="272"><figcaption><p>Set Input Value in Data Design block</p></figcaption></figure></div>

The behavior of the block is similar to the [Set Input Value](/app-editor/page-flow/toolbox-blocks/set-input-value.md) block, with some important differences:

* Works only with elements generated using [Content from Data Design](/app-editor/page-flow/toolbox-blocks/content-from-data-design.md) block that are dynamically added.
* Element Selection: You can only choose an element placed inside the selected [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element.

The block consists of the following (from top to bottom):

* *Data Design*: [Selectable Input](/app-editor/page-flow/block-anatomy.md#selectable-input) to choose the [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element whose element you want to target.
* *Element*: [Selectable Input](/app-editor/page-flow/block-anatomy.md#selectable-input) to choose the element, within the selected [Data Design](/app-editor/page-editor/built-in-elements/data-design.md), you want to set the value of.
* *ID*: Optional [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*text*](/app-editor/page-flow/references/value-types.md) value representing the unique value that was provided to the [Content from Data Design](/app-editor/page-flow/toolbox-blocks/content-from-data-design.md) block. See below for more details.
* *ID2*: Optional [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*text*](/app-editor/page-flow/references/value-types.md) value representing the secondary identifier that can be used to identify the desired element. See below for more details.
* *Data*: [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts the value to set (of type [*text*](/app-editor/page-flow/references/value-types.md)*)*

***

## ID and ID2 usage

The behavior of this block depends on the ID and ID2 [value parameters](/app-editor/page-flow/block-anatomy.md#value-parameters) and is detailed below:

* ID and ID2 not provided: Operate on the selected element for all generated instances of the same [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element.
* ID2 provided and ID not provided: Operate on the selected element for all generated instances of the same [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element with the same ID2 value.
* ID provided and ID2 not provided: Operate on the selected element for all generated instances of the same [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element with the same ID value. Since we recommend the ID value to be unique, this would choose one from all the generated instances of the associated [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element.
* ID and ID2 provided: Operate on the selected element for all generated instances of the same [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element with the same ID  and ID2 value.&#x20;

***

## Usage Examples

{% hint style="info" %}
**NOTE: Please refer to the prerequisite information shown** [**here**](/app-editor/page-flow/references/prerequisite-for-dynamic-content-block-examples.md) **before seeing the example.**&#x20;
{% endhint %}

The image below shows an example in which the [Input](/app-editor/page-editor/built-in-elements/input.md) element (*Input43*) for the owned quantity is set to the value of variable *b* (which has the value of *50*) for Company 1, which as rendered with the ID *ST100* .

<div align="left"><figure><img src="/files/EP6LlkZ4UmtpUOxNv41P" alt="" width="518"><figcaption><p>Set Input Value in Data Design block example 1</p></figcaption></figure></div>

The result of the above example is highlighted below, where the owned quantity [Input](/app-editor/page-editor/built-in-elements/input.md) element (*Input43*) is filled with the value *50* for Company 1.

<figure><img src="/files/3paa5eDGLE4y3l3VIOD2" alt=""><figcaption><p>Result of example 1</p></figcaption></figure>

In the second example, we will demonstrate the scenario where neither ID nor ID2 are provided. In this case, the system will populate the owned quantity [Input](/app-editor/page-editor/built-in-elements/input.md) element (*Input43*) for all generated instances.

<div align="left"><figure><img src="/files/gRRfHdlrpUm5Z5lHHO0I" alt="" width="463"><figcaption><p>Set Input Value in Data Design block example 2</p></figcaption></figure></div>

The result of the above example is highlighted below where the owned quantity [Input](/app-editor/page-editor/built-in-elements/input.md) element (*Input43*) is filled with *0* for both the companies.

<figure><img src="/files/vqjIKSqxJp1b7U6be5Im" alt=""><figcaption><p>Result of example 2</p></figcaption></figure>


---

# 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://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/set-input-value-in-data-design.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.
