Room Data Sheets Graph (2.0.2)

Hello All,

Long time forum lurker here, and genuinely stuck on this graph. Am attempting an automated Room Data Sheet (RDS) - got this far, having started this morning. Generating a number of errors - anyone got any pointers/tips on where I’m going wrong?

Dynamo 2.0.2 & Revit 2019.0.2 : Link to all files here.

Just the .dyn here:

Room Data Sheet_Plans Elevations RCP 3D (Version 2.0.2).dyn (135.3 KB)

Generating the following errors:

…not renaming some views correctly, as I’ve mishandled my lists probably.


Try putting a “Transaction.Start” node after the Transaction.End node. I think this is going to resolve the first error and see where that gets you.

@jean am I using your package as intended, or should I review the workflow?

@SeanP thanks for the tips. Applied the same logic to the creation of all types of views.

New .dyn : Room Data Sheet_Plans Elevations RCP 3D (Version 2.0.2).dyn (145.6 KB)

Testing on Dynamo 2.0.2 & Revit 2019.0.2 with 4 rooms on Level 0 view.

Now returning only two errors:

First Error:


Feeding the Quasar node 4 fresh views:

Resulting in this:



Second Error:

Something is throwing off the set parameter by name node - but its actually working fine.


This is what is created (Elevations are not renamed - because my listing is wrong? )

  1. Clear any rooms that aren’t placed. There are nulls in the Elevation results. Also make sure your list structures are the same here. It actually looks like the Rooms node and Floor Plan View may be feeding different length lists to the Elevation node. I would flatten them both and see.
  2. Try to rename your rooms and see if that helps.
  3. I think your transactions need some work. I would look at a Wait node from python or a package like Orchid. This may help sequence your steps a little more between the creation of dependent items and really it looks like everything just needs to wait on the Floor plans.
  4. The Set Parameter by name is failing because you haven’t connected the Room number and Room name to the node that combines them with “Isomettic View”.
1 Like

Hi @Wayne_Patrick_Dalton,

Has this been developed further following @SeanP’s advice? I have tried following along but unfortunatley had no luck.

Can you share what you have and we can try to help?

Hi @SeanP,

Thanks very much for getting back to me. Please find attached screenshot and dynamo script. The script was created in Dynamo version 1.3.46666 & Revit version 2019.2.2. As you can see from the screenshot I am having issues with the nulls in the elevation node & creating any RCP’s at all. I am using the standard revit architectural sample project for testing.

What is the warning message above the ElevationInRoom node?


See below screenshot. Its similar to the issue above, it is creating elevations but also creating unwated nulls. Apologies I am unable to attach the script, I have sent it to you via Linkedin. image

From my testing, it appears there is a lacing issue inside the node that is causing the nulls. When I testing it with the FirstItem node for room and view, it works without an issue. @jean do you have any information?

I am not sure if it is an option, but I would also recommend that you update Dynamo and/or use 2.* version so you can update to the latest Quasar package as well. This may resolve the issue since the v.0.2.0 is several updates old.

Also, if you view the GitHub for the package examples, you can see the video for this shows a single level being supplied and not a list.

1 Like

Thanks very much for your help sean. I was able to resolve the issue by changing the lacing to longest. Did the ceiling node work for you by any chance? I cannot get that node to work at all.

Not really sure why that node isn’t working, but I have modified the Floor Plan Node by Archilab to create ceiling plans like this in the past in a python node.


# Copyright(c) 2015, Konrad K Sobon
# @arch_laboratory,

import clr
from Autodesk.DesignScript.Geometry import *

# Import Element wrapper extension methods
import Revit

# Import geometry conversion extension methods

# Import DocumentManager and TransactionManager
import RevitServices
from RevitServices.Persistence import DocumentManager
from RevitServices.Transactions import TransactionManager
doc = DocumentManager.Instance.CurrentDBDocument

# Import RevitAPI
import Autodesk
from Autodesk.Revit.DB import *

import System
from System import Array
from System.Collections.Generic import *

import sys
pyt_path = r'C:\Program Files (x86)\IronPython 2.7\Lib'

#The inputs to this node will be stored as a list in the IN variable.
dataEnteringNode = IN

if isinstance(IN[0], list):
	rooms = UnwrapElement(IN[0])
	rooms = [UnwrapElement(IN[0])]
names = IN[1]
bboxOffset = IN[2]
runMe = IN[3]

def OffsetBBox(bbox, offset):
	bboxMinX = bbox.Min.X - offset/304.8
	bboxMinY = bbox.Min.Y - offset/304.8
	bboxMinZ = bbox.Min.Z - offset/304.8
	bboxMaxX = bbox.Max.X + offset/304.8
	bboxMaxY = bbox.Max.Y + offset/304.8
	bboxMaxZ = bbox.Max.Z + offset/304.8
	newBbox = BoundingBoxXYZ()
	newBbox.Min = XYZ(bboxMinX, bboxMinY, bboxMinZ)
	newBbox.Max = XYZ(bboxMaxX, bboxMaxY, bboxMaxZ)
	return newBbox

	errorReport = None
	if runMe:
		viewTypes = FilteredElementCollector(doc).OfClass(ViewFamilyType)
		for i in viewTypes:
			if i.ViewFamily == ViewFamily.CeilingPlan:
				viewTypeId = i.Id
		existingPlans = FilteredElementCollector(doc).OfClass(View).ToElements()
		existingPlanNames, existingPlanElements = [], []
		for i in existingPlans:
			if not i.IsTemplate:
				if i.ViewType == ViewType.FloorPlan:
		# Start Transaction
		floorPlans = []
		for i,name in zip(rooms,names):
			levelId = i.LevelId
			bbox = i.BoundingBox[doc.ActiveView]
			newBbox = OffsetBBox(bbox, bboxOffset)
			viewName = name
			if viewName in existingPlanNames:
				view = existingPlanElements[existingPlanNames.index(viewName)]
				view.CropBox = newBbox
				view.CropBoxActive = True
				view.CropBoxVisible = False
				newView = ViewPlan.Create(doc, viewTypeId, levelId)
				newView.ViewName = viewName
				newView.CropBox = newBbox
				newView.CropBoxActive = True
				newView.CropBoxVisible = False
		# End Transaction
		errorReport = "Run Me set to False"
	# if error accurs anywhere in the process catch it
	import traceback
	errorReport = traceback.format_exc()

#Assign your output to the OUT variable
if errorReport == None:
	OUT = floorPlans
	OUT = errorReport


Thats brilliant, I put the NAME to IN[1] & ROOMS to IN[0] and it worked perfectly. Thanks so much. Now to place all created views onto sheets.

1 Like

@SeanP, Good day. Yes, you are absolutely right and thanks for pointing out. @chris.millar, the intention of the ViewUtility.ElevationInRoom was to generate the views Level by Level . Currently, Quasar package version 0.2.x are the most stable versions so far …

1 Like

Any thoughts on the RCP node? Is it a usage thing or the node?

@chris.millar, @SeanP, i think, usage… :smile::grin:
can refer to this one :point_down: …? or Archilab one?

Ha, well I would agree except I did feed it singles and just got a completely non-descript error message that it couldn’t be completed. I’ll get and post the actual error, but it wasn’t something I had seen before.

Wow, I feel pretty dense that I didn’t notice the Python code on the very page of yours that I linked too! I know I had posted similar code for RCP nearly two years ago, funny how things cycle back through.

@SeanP, its ok :grinning: . I think, your previous post is a solution here too …

@jean, Wanted to make sure I closed the loop here on what I was seeing. I think it has all the information it is supposed to have, but provides error.