-
Notifications
You must be signed in to change notification settings - Fork 188
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
Element.SetParameterByName Beams . z Justification #3020
Comments
import clr #This is .NET's Common Language Runtime. It's an execution environment import sys #sys is a fundamental Python library - here, we're using it to load in import System #The System namespace at the root of .NET clr.AddReference('ProtoGeometry') #A Dynamo library for its proxy geometry clr.AddReference("RevitNodes") #Dynamo's nodes for Revit import Revit #Loads in the Revit namespace in RevitNodes clr.AddReference("RevitServices") #Dynamo's classes for handling Revit documents clr.AddReference("RevitAPI") #Adding reference to Revit's API DLLs import Autodesk #Loads the Autodesk namespace doc = DocumentManager.Instance.CurrentDBDocument #Finally, setting up handles to the active Revit document Viga.SetParameterByName("z Justification", 2) TransactionManager.Instance.TransactionTaskDone() |
SOLVED: in a 2022 Post |
Issue Description
Please fill in the following information to help us reproduce the issue:
Dynamo version
Dynamo:
2.13.1.3887
Operating system
OS:
Microsoft Windows NT 10.0.19045.0
What did you do?
I was trying to change the z Justification in a Beam using the "Element.SetParameterByName" method (I tried both Dynamo modules and Python) and I get this error Element.SetParameterByName Operation Failed. specTypeId is not a measurableSpec (ForgetypeId). Parameter name: specTypeId
What did you expect to see?
A change in the z Justification. In previous versions of Revit that method and the z Justification parameter works fine.
What did you see instead?
(Fill in here)
What packages or external references (if any) were used?
Stack Trace
CLR:
4.0.30319.42000
The text was updated successfully, but these errors were encountered: