In Revit, Tags may reference elements in the current Document, or they may reference an element in a Linked document. There are a number of useful properties that can be obtained from a Tag that references a Linked document. This node returns a list with sublists which include the source element Id, and information needed to determine which document the element resides in.
This will take a list of Strings, a single string to ‘find’, and another list to Filter. If it finds a match in the string list, it will allow the matching ‘filter list’ element/s through, and will show them in the Matching output node. Essentially this a wrapper for String.Contains and List.FilterByBoolMask to make it a little easier to use.
Everything about this node is pretty much the same as the Form.ByLoftCrossSection, except it can create multiple loft forms based on the lists structure passed into it and assign them to be solids or voids based on a list of boolean values (true / false).
Form.ByLoftCrossSections is one of two OOTB Dynamo nodes available in Revit that produces a type Form geometry (native Revit geometry). It requires the input of a ModelCurve which you can get from either a Modelcurve.ByCurve or a ModelCurve.ReferenceByCurve. You can only use this node in a family as both the ModelCurve and Form.ByLoft nodes will only work in family environment.
If you pass a false into the isSolid you will get a void rather than a solid.
If you need a more complex geometry in Revit, take a look at the Form.ByGeometry node from Spring Nodes.
Form.ByGeometry “bakes” any solid, polysurface or surface passed into it into the active Revit family environment as a Free Form Element type (native Revit geometry). This should be used in the place of ImportInstance.ByGeometry in every instance. (a similar result can be achieved with the FamilyInstance.ByGeometry from a project level). In some cases you should even see handles appear which will allow you to manipulate the goemetry to some level once it is “baked” into Revit.
Using some python coding which you can find here, it is rather easy to set a section box to a scope box in a 3d view.
There are a couple of ways to go about this (all of which require Springs Nodes):
In the end though, the results are pretty much the same. You should end up with native Revit, free form elements, some of which will even display handles which can be used to edit this geometry (usually simpler, rectilinear geometries such as boxes will be fully editable, other times things like lofted geometries might have and end face that is editable).
Be aware that there is a scaling issue currently with dynamo’s SAT import nodes where the they only read the geometry as though it were in meters, but this can be easily fixed through some creative scaling before “baking” it into Revit.
This workflow can also be used to bring SAT information into Revit from Inventor as well.
Using a 1:1 set of Views and Elements to override, this node will override the projection lineweight for those elements in the matching view.
This node finds the Crop Boundary elements for a list of views. Thanks to Dimitar Venkov at this link.
This node attempts to get all useful properties from the Worksets in the current Revit document, including:
· The internal workset element
· Workset Ids
· Workset Names
· If the Workset is open or not (Boolean)
· If the Workset is visible by default or not (Boolean)
· If the Workset is the default Workset (typically Workset1, again a Boolean result)
The output is multiple lists of matching length. This node was based on a similar one in the archi-lab package.
Dynamo Nodes 