Parameter Mapping – Planworks Support Center

How to transfer parameter values automatically between rooms, floors and ceilings.

In this article

What is parameter mapping?
Opening the mapping rules
Creating a rule
Combining values
Using templates
Applying to existing elements
When a rule doesn't work

What is parameter mapping?

Parameter mapping makes Rubia copy values from one element to another. Typical cases: the room number should appear on the floor, or the floor type should be written to a room parameter so it shows up in the room data sheet.

Opening the mapping rules

In the main window under Miscellaneous, click Parameter Mapping, or Edit mapping rules in the Settings. The “Edit parameter mapping” dialog opens.

Creating a rule

Add a rule

Click the plus button at the bottom left (Add rule).
Choose the source

Under From category, choose where the information comes from (rooms, floors or ceilings), and under Take information from the parameter.
Choose the target

Under To category and Write to parameter, define where the value is written.
Save

OK saves the rules. They run every time you apply from now on.

Examples

From category	Take information from	To category	Write to parameter
Rooms	Number	Floors	Comments
Rooms	Name	Ceilings	Mark
Floors	Type Name	Rooms	Floor Finish

Combining several values

You can combine several parameters into one text, e.g. room number room name. In the naming logic editor, double-click a parameter to insert it.

Good to know

Combined expressions, multiple layers or the UniqueId need a text parameter as target. The ElementId can be written to a text or integer parameter.

Using templates

Under Templates you save rule sets and load them in other projects. Useful if your projects are always set up the same way.

Applying mapping to existing elements

In the Settings you'll find the option Always apply parameter mapping. When enabled, Rubia also applies your rules to existing elements that aren't newly created. You need this, for example, if you created rules after the elements had already been generated.

When a rule doesn't work

Message	What's behind it?
Source and target parameter types are incompatible	E.g. text into a number parameter. Choose a matching target parameter.
Target parameter is read-only	The parameter can't be written (e.g. calculated or locked by Revit).
Source/target parameter is not found	The parameter doesn't exist on the element. Check spelling and category.
This target parameter is duplicated	Two rules write to the same parameter. Remove one of them.
The target parameter did not retain the mapped value	Revit didn't store the value, usually because of a format mismatch.