Dynamo packges in 2025 revit

[essam.rashad]

im trying to create a simple script that allowes me to make a section box around linked element , make in mind that i have the element ID , but whenever i try to search , the nodes are not compatible with each other somehow ,
the alghorithm that im thinking of is ,

getting all links > get all instances from them > filter to get the element by the id i typed > make section box around it ,

only node i started with and i cant go on is select.getdoucments and i stopped at this point .
can you please help?

[BimAmbit]

iirc, these nodes are available ootb in rvt 25:

[essam.rashad]

i think i already made it with select.get doucments node but whats next? thats what im currently cant get , i want to get all instance elements from all links

[BimAmbit]

better off prompting UI selection to link element first, query its bounding box, create a view and confine it with that bounding box.

selection: DataShapes
boundingbox: OOTB
view creation: OOTB i think?
confinement: Rhythm

DataShapes - select linked model elements

Hi, is it posible to select linked model elements with data shapes? I use this node(below) and my script works only with my elements not linked… [image]

Set Section Box of 3D View

I’ve tried View3D.SetSectionBox and it doesn’t work. My approach is to use a Scope box for overall boundingbox corners. [image] Result: [image] Testing with boundingbox of an element doesn’t work either: [image] Nor does built-in node AxonometricView.ByEyePointTargetAndBoundingBox: [image] I’m using Revit 2017.2 and Dynamo 1.2.1.3083. It seems something deep has changed. Maybe the Revit API? I’ve posted an issue on dynamo github site no response yet.

i want to get all instance elements from all links

unnecessary also not that straightforward. this might involve filtering by view dependency first, culling all element types, getting all things under model categories and etc. a bit tedious i reckon unless there’s a package to give a bit of shortcut.

besides, a free plugin named “CoinBox” does this. but if you are doing this for learning dynamo, targeting specific subset of categories would be easier since when you filter all instances, instances from non-model categories might confuse you.