Element Properties in Hotlinks

Use Import/Export Properties to ensure that everyone uses the same Element Property set.

See Export/Import Properties Between Projects.

However, if a Hotlinked Module does contain different properties than the host file, then you can manage them based on the following use cases:

•

Hotlinked Module Contains New Properties

•

Hotlinked Module Contains Identical Property With Conflicting Definition

Hotlinked Module Contains New Properties

If the Hotlinked Module contains new properties (or groups) which don’t exist in the host project, these are appended to the list in Property Manager, and are shown in gray:

Properties from Hotlinked Modules

•

Are searchable, like any property

•

Can be scheduled, like any property

•

Cannot be edited or deleted in the host project; they can be edited only in the external file.

For each such property or group, you have the option to merge it into the host project: click the Merge icon at the end of the row in Hotlinked Manager.

Once the property is merged, it becomes a fully editable part of the host project.

A merged property loses its connection to the external file (any changes to this property in the external file will not be reflected in the host file).

Hotlinked Module Contains Identical Property With Conflicting Definition

Properties are considered identical if they have the same name and are in the same group.

However, a Hotlinked Module might contain an identical property as the host file, but with conflicting property definitions. For example, the two properties have the same name (e.g. “Fire Resistance Rating”), but with a different data type (e.g. Tag List instead of Option Set) or availability.

In this case, the Hotlinked Module’s property is in conflict with that of the host file: the conflicting property is appended to the list in Property Manager, but is shown only if you check Show conflicts with Properties in Hotlinks.

For each such property or group, you can do one of the following:

•

Click the Merge icon at the end of the row in Hotlinked Manager. The property from the Hotlinked Module, with its definitions, will override the corresponding property in the host file. (The host file property’s definitions now match those of the hotlinked file property, until you change the definition of any one of them.)

•

Open the external module file, and edit its property definition so that it matches that of the host file. Then, in the host file, update the Hotlinked Module to eliminate the conflict.

•

Do nothing. In this case, when the property values of these hotlinked elements are scheduled, the values will be converted to match those of the corresponding project properties.