Warning appears when opening Revit family documents, how to skip the warnings and report them?
In some cases opening a family document for example open in the background with Dynamo or editing the family from Revit project file or just opening the revit family file from Revit.
The warning says something wrong in the family was not allowed then Revit resolved removing nestee elements or geometry from it and gives you the option to click okay delete or cancel. I would like to hit the button okay and get a report debugging for each file that does this when opening.
It is very annoying because scripts stop opening filea in background unless you choose an option in the emerging revit warning window.
I know this kind of warning is due a dimension length parameter is wrong so the geometry breaks not possible to generate but you see this when opening the file.
FWIW, due to the pains of various Python engines it might be a good time to transition to a C# node to do the opening and processing. Depending on what actions you want to do could be as simple as one node to do all the processing.
I usually pretend to resolve all script in one single python node because the outputs would be enormous lists that take ages for Dynamo to respond. I could try zero touch nodes as well but I try to skip mixing code languages and overusing external libraries because need to install more shit in all computers of whoever is going to run the scripts
Most of the time you have a choice. You can manage âwhich version of the graph to run in which Revit versionâ and hope users open the right one, or you can have the same graph for all versions but with different packages. Either way you are managing the content.
One package called âArubans awesome bulk processing toolsâ, publish it locally or to package manager for each Revit build in the ecosystem, and youâre done.
Packages, Revit and Dynamo versions, incompatibilities or changes in Revit API, IT with admin rights every time something changes and updating. I just avoid that with python script that works anywhere, so keep that focus until I see itâs not worth or something better available. If i make this failure processor work will post code snippet.
