How To Use Entity Properties To Set Device Location


Entity properties are features you can use to set additional visible or invisible labels on devices. These are similar to setting attributes on a block definition, but are registered in the project database so they can be used in data export, tables and riser generation after they are set on the devices. You can add as many entity properties to any device and control the visibility whether they are shown in the device attribute or not.

Setting Device Locations

While most entity properties are arbitrary, some properties are used for specific program features. 'Location' is one of these properties and can easily be set on devices on your drawing.

To begin, use the command 'Set Entity Properties' on the 'Entity Properties' ribbon panel-


You will be prompted to select devices you would like to add properties to. Make your selection and then press enter.


Next, you will be prompted to type a name for the property. Type 'Location' and press enter-


You may select a string on the drawing to get the property value, but if no reliable room number or name exists you can use the keyword 'T' to type a value-


Type your desired location string and press enter-


This applies the value to the selected device attribute(s) and is visible by default-


While the location properties are visible, generating risers and the device schedule reports will carry this value over as well, as shown below-



When you have generated your reports and risers, you may want to hide all the location values on the floor plan before publishing your drawings. To do this use the 'Set Attribute Visibility' command on the 'Attributes' ribbon panel-


This will open a dialog with all named device and entity properties in the current project. You can uncheck the 'Visible' setting for the property name you want to globally turn off. This will hide the selected named properties in the drawing device labels, while leaving the the labels visible on the generated riser devices and reports.




Was this article helpful?
0 out of 0 found this helpful