-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All Elements Of Category fails for views #2970
Comments
Fun fact: in 0.6.3 this used to work... |
Its because of the new Revit API that now includes view templates in a view category. I wrote a node for this: http://archi-lab.net/?p=1074 |
No, @ksobon , that can't be the reason. When I try this on top of Revit 2014 with 0.6.3 it works and with 0.7.3 it doesn't. So obviously it's Dynamo, not the Revit API. It seems like Dynamo 0.7.x is handling (some) warnings/exceptions differently. |
You are both correct. @ksobon is correct that the template view thing is causing headaches, and @andydandy74 is correct that this worked in 0.6.3. We changed the way that we do this filter collection in 0.7.x and didn't account for the new functionality that throws this exception. Tracking internally: |
any update here? still there in RC2 0.7.5. |
I have Dynamo 0.8.0.950 and this is still an issue? How do we deal with this View Template Error? |
Mhmmm, can we get this solved? It would be nice. Thanks! |
Duplicated by #2313 |
@ikeough Still an issue in 1.0.1 on Revit 2016 r2. Can we get this solved. It looks like its been around for a while now. |
We'll get his for 1.2. Sorry, this one fell between the cracks. |
A fix attempt is made, see Pull request as reference: DynamoDS/DynamoRevit#1239 |
Fixed in 1.2. |
👍 |
The warning is slightly different thought; "Warning: ElementQueries.OfCategory operation failed. |
Using
All Elements Of Category
on the Views category will results in the following warning:Warning: ElementQueries.OfCategory operation failed. View cannot be a template view.
The same happens when using
All Elements Of Type
The text was updated successfully, but these errors were encountered: