Good morning,
I’m having a problem using the node “Document.Views” where it’s getting views that currently don’t exist on the document. They existed before, but they were erased. Somehow dynamo understand they still exist on the model, and I don’t understand why and how to solve it. Could I get some enlightenment here?
Thanks in advance!
That’s odd. Try restarting Revit and running the script again—it might clear any cached data. Also, double-check the View Schedule to confirm whether the views still exist in the model. If the issue persists, we can help dig deeper.
Hi @JoseLP is Document.Views node a costum one ? but guess you can disconnect and run and connect run again depends…or use document views from genius loci think it have option for refresh, or try force run from datashapes in the extension bar
It’s a Clockwork node. I also tried to extract its python code to avoid custom node errors, but I got same result. I just tried using Genius Loci one, and it works as it should now.
Anyway it’s strange that I can see and select those erased views using the Revit node “Views”. I wish I could understand why Revit is doing that. Oh, I’m using 2025 version, forgot to mention before.
@_Vijay I checked views schedule also, and those views are not there. It’s a dynamo thing retrieveng cached data I’m guessing, but I never had this issue before.
Thank you for your time both!
Hey,
Yeah something to do with element binding… @jacob.small is the expert…
Have a look at P.37 https://static.au-uw2-prd.autodesk.com/Class_Handout_AS323853_Jacob_Small.pdf
Hope that helps,
Mark