# Select Data

## Overview

![The Select Data Node.](/files/uH4qevvDExKXyN0DRSHh)

Because **Input Data Sockets** in **Incari** can only receive a value from a single connection, this creates a problem when you wish to converge the **Logic** into a single branch. This is why the **Select Data Node** was introduced. The **Select Data Node** takes two or more pairs of **Pulse** and **Data** inputs, and outputs the value corresponding to the input **Pulse** that the **Node** was executed by.

[**Scope**](/incari-studio/2023.1/toolbox/overview.md#scopes): **Project**, **Scene**, **Function**, **Prefab**.

## Attributes

![The Select Data Node Attributes.](/files/IbUeB4sxseLN3qTpGGNi)

| Attribute   | Type          | Description                                                                   |
| ----------- | ------------- | ----------------------------------------------------------------------------- |
| `Data Type` | **Drop-down** | The type of data that will be plugged into the `Input` **Sockets**.           |
| `Count`     | **Int**       | The number of **Input Pulses** and **Data Values** the **Node** will receive. |

## Inputs

| Input       | Type                                          | Description                                                          |
| ----------- | --------------------------------------------- | -------------------------------------------------------------------- |
| `Pulse [n]` | **Pulse**                                     | The **Pulse** corresponding to the **Data** in the **Socket** below. |
| `Input [n]` | *Defined in the `Data Type`* ***Attribute**.* | The **Data Value** corresponding to the above **Pulse**.             |

## Outputs

| Output             | Type                                          | Description                                                                                                                            |
| ------------------ | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse**                                     | A standard output **Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |
| `Output`           | *Defined in the `Data Type`* ***Attribute**.* | The **Data Value** received in the `Input` **Socket** corresponding to whichever `Pulse` triggered the execution of the **Node**.      |

## Example Usage

The **Select Data** **Node** is particularly useful for optimizing our **Logic** workflow in order to avoid repetition of **Nodes**. The following example shows how to use the **Select Data** **Node** to merge two branches of **Logic** into a single branch.

![](/files/MnCX0bSgT2XYtnEGxzFr)

The image above shows two branches that have the same effect (modify a **Text** **Object**) and could converge into a single branch. For this, the **Select Data** **Node** is introduced:

![](/files/pxeIRhkyfx9cN0Zmsnv9)


---

# 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.incari.com/incari-studio/2023.1/toolbox/flow-control/select-data.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.