# Parameters

**Category**: App Studio

**Version**: 1.0

**Last Updated**: March 2, 2026

**Author**: Any2Info

### Description

The **Parameters** tab in the property menu of Dashboards and Forms allows configuration of:

* Incoming Parameters
* Fixed Filters

Together, these mechanisms provide controlled data filtering at the dataclip level.

Incoming Parameters define filterable inputs for specific dataclips.\
Fixed Filters assign values to those parameters automatically.

All filtering logic is applied using **AND** conditions.

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FCERZD4KyNnGpYsETdNgi%2FImage%20incoming%20parameter%20-%20data%20-%20form.png?alt=media&#x26;token=0a7b7501-03a4-40a4-9a3b-9d99642fd991" alt=""><figcaption></figcaption></figure>

***

## Incoming Parameters

### Description

An Incoming Parameter defines a filter input for a specific:

* Dataclip
* Header (field) within that dataclip

It allows external or internal processes to inject a value that filters the dataclip’s data.

Each parameter is strictly bound to **one dataclip and one header**.

***

### Configuration Options

| Setting     | Required | Description                                                           |
| ----------- | -------- | --------------------------------------------------------------------- |
| Name        | Yes      | Recognizable identifier of the parameter.                             |
| Description | No       | Informational description used for management purposes.               |
| Dataclip    | Yes      | The dataclip to which the parameter applies.                          |
| Header      | Yes      | The specific header (field) within the selected dataclip.             |
| Required    | No       | If enabled, data will not load unless the parameter receives a value. |

***

### Type Handling

The parameter type is implicitly determined by the selected header type.

Examples:

* Numeric header → Numeric parameter
* Date header → Date parameter
* Text header → Text parameter

Type validation follows the dataclip header definition.

***

### Behavior

* A parameter applies only to its configured dataclip.
* Multiple parameters can target the same dataclip.
* When multiple parameters apply to the same dataclip, they are combined using **AND** logic.

Example: UserId = 12 AND Department = 'Sales'

***

### Best Practices

* Use **Required** for sensitive datasets.
* Use **User** type filters for row-level security.
* Avoid multiple parameters targeting the same header.
* Use Variables carefully when allowing user-editable values.
* Logically separate system-driven filters (Fixed) from navigation-driven parameters.

***

### Changelog

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