Skip to main content
Skip table of contents

Create or Update Revit Rooms from Linked Revit Model

Often Revit models are linked in to other Revit projects. Once a model has been linked in to the host model, those working on the host model can reference the Room extents to place their Family Instances and other elements accordingly. If the Rooms in the linked model have already been linked to Rooms in dRofus, those working on the host model can conveniently create and / or update their Rooms (within the host model) to correspond with the Rooms in the linked model. Additionally, if Item occurrences for these Rooms have been planned in dRofus, and the Family Types in the host model have already been linked to Items in dRofus by those working on the host model, they can then easily view and validate the Family Instances within their Revit Rooms using either the "Items in Room", or "Items in level/model" window. 

To Create / Update Rooms in the host model (based on Rooms in the linked model), select "Linked model Rooms - > Rooms":



By default, all linked models that are Room Bounding will be selected:



If you create Rooms by copying from Rooms in a linked model that is not room bounding, it will be set as Room Bounding when you copy them.


Info

If Rooms within the linked model has design options, you are able to restrict creation of Rooms by copying only from Rooms that are in the primary design option by selecting the following check box:



Also, see: Working with Revit Design Options.


Click on "OK" to create the Rooms from the selected linked model(s), and then a message similar to the one below will then pop up, summarizing the total number of Rooms created / updated as well as the total number of Rooms that were not (due to the chosen key parameter within Rooms in the linked model being either not unique or empty):


When creating / updating Rooms from a linked model, it is important to take note of the active Room Attribute Configuration:



The above command will use the mapping of the "Key Attribute used for comparing" in order to find Rooms within the linked model to those in dRofus, after which it will then push and pull values as per the mapping of other Attributes / Parameters.

In the example above, the active Room configuration called "Revit Rooms - Update" uses dRofus' "Room ID" as the Key Attribute (the value of which gets pushed in to the host model's corresponding Room parameter), and in addition has been mapped to bring in values of "Dept (Name)", "Designed - Programmed %", "Note" and "Room Function #" from dRofus Rooms in to "Department", "drofus_room_des_prog_%", "Comments" and "drofus_room_func_no" respectively in Revit Rooms as follows:



Hence the values have been brought in to a new / updated Room within the host model as follows:



Also note that during the above command, the "Number" and "Name" parameters within the host model's Rooms will always get values copied across from these parameters within the linked model's Rooms (even though these may not be mapped to be brought in from dRofus Rooms within the active Room configuration):



Often Rooms will change within the linked model - i.e., Rooms can be added, deleted, moved, changed in shape and size etc. Once the updated linked model has been re-issued and re-loaded as a link to the host model, those working on the host model will again need to carry out the above process in order for the Revit Plug-In to transfer all of the updates to the changed Rooms.

If there are any Rooms in the host model for which there are no longer any corresponding Rooms in the linked model - the next time the linked model is reloaded within the host model and when carrying out the above command to update Rooms within the host model, the Plug-In will ask if you'd like to "Delete Superfluous Rooms".


Level Names Mismatch

If the host and linked Level names do not match when creating / updating Rooms within the host model, you will get the following message:



You will need to ensure that the Level names are consistent between the models.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.