# Parameters

A parameter is a piece of information that defines or describes a family, for example, its size, material, or identifying tag. By default, each file includes parameters such as *Comments, Mark, Keynote, Type Mark,* and *Workset.* Parameters can be either type (shared across all instances of that family type) or instance (unique to each placed element). To add additional parameters, use [P](/beam/beam-for-rhinoceros/parameters.md#custom-parameters).

![](/files/YAoasu7JTCuOmnaAejC5)

Select one or more object that belongs to a family or a block to edit its parameters using the [Panel](/beam/beam-for-rhinoceros/using-rhino-beam.md#panel).

Use [Q](/beam/beam-for-rhinoceros/parameters.md#scheduling-family-parameters) to query and edit in a table format.

## Custom parameters

Besides the default parameter you can include as many parameters as you like in the Rhino file.\
To add additional custom parameters to families use [P](/beam/beam-for-rhinoceros/parameters.md#custom-parameters) on the panel.

![](/files/nX8W7ycTZIFOBN9lJEQq)

Press Add to create a new parameter or Edit to edit an existing one. Remove will delete the selected parameters from the Project.

Parameters can also be grouped into property sets. Press Property Sets to manage them.

{% hint style="info" %}
A property set is a collection of parameters that can be applied together, making it easier to manage consistent data structures across families and projects.
{% endhint %}

![](/files/VfQarnOkFVZGDl1WSovy)

Parameters can hold different kinds of data:

* Text – stores words, codes, or notes.
* Integer – stores whole numbers (e.g. 3, 45).
* Number – stores decimal values (e.g. 2.5).
* Length – stores dimensions with units (e.g. 1200 mm).
* Area – stores values in square units (e.g. m², ft²).
* Volume – stores values in cubic units (e.g. m³, ft³).
* URL – stores hyperlinks.
* Yes/No – stores a simple true/false value.

Parameters are defined as type or instance.

* Instance parameters are unique to each placed element.
* Type parameters are shared by all instances of the same family type.

{% hint style="warning" %}
In Revit, parameters must already exist to receive data imported from Rhino.\
Make sure to create the necessary Project Parameters in advance so that values from Rhino can be mapped correctly.

In Revit, parameters are filled based on their data type: numerical parameters require numbers, length parameters require valid dimensions, and so on. If the value from Rhino does not match the expected type, the parameter will remain empty without any warning. Always verify your data after importing.
{% endhint %}

## Importing and exporting parameters

{% hint style="info" %}
.txt (Shared Parameters) – a Revit-native format, used to keep parameter definitions consistent across projects and families.\
.json (BEAM) – a BEAM format, used to transfer, back up, and reuse full sets of parameters inside Rhino.
{% endhint %}

You can import and export parameters as *.json* files.\
This allows you to save parameter sets from one project or family and reuse them in another. 

Press Export to save a *.json* file to create a snapshot of your current parameters, and later import it to restore or share the same setup.

Press Import to choose the *.json* file, to import all parameters into your project.

### Importing shared parameters from Revit

You can import parameters from a Shared Parameters text file.\
A *Shared Parameters file* is a central *.txt* file that stores parameter definitions so they can be reused consistently across multiple projects and families.

Press Import to choose the *.txt* file, then select the parameter you want to bring into your project.


---

# 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://wiki.mksdtech.com/beam/beam-for-rhinoceros/parameters.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.