Hey everyone!
Since Revit 2023 came out there have been quite a few issues with the SetParameterByName node due to API changes.
It looks like the hotfix is out and it is working as expected now! (see below)
The download can be found in your manage.autodesk.com account and I highly recommend everyone get it installed ASAP if you are using 2023.
https://help.autodesk.com/view/RVT/2023/ENU/?guid=RevitReleaseNotes_2023updates_2023_0_2_html
Hi I am trying to understand why the Element.SetParameterByName wont work for me and how I work around it. I am not an expert at programing but know enough to screw things up.
[Screenshot 2022-07-12 16.40.42]
In the screeenshot included here, I can’t figure out how to utilize UnitUtils.IsMeasurableSpec(ForgeTypeID) Any help would be appreciated.
What am I trying to accomplish? I am trying to set a shared Parameter value for each Area in an Area plan, which assists in calculating occupany loa…
Hi!
I had a script that worked with revit 2021 and now with revit 2023 stopped working the node of set element parameter by name, regarding beam justification.
This is what I get for Y justification that worked before. The same thing happens with Z justification.
[Dynamo]
I believe it has something to do with the new API changes, since it worked before. If I put true or false it gives no error, but is for properties with checkboxes and not this one with 4 options.
Any help? Anyone else has…
Has anyone tried to set worksets with the new Dynamo release that comes with Revit 2023?
[image]
I cannot set worksets anymore on a graph that worked in the past with ootb nodes…
[image]
Just returns nulls…
Hi
I dowloaded Revit 2023 with the lates dynamo but I cant get the Element.SetParameterByName node to work any more. What is I have a Yes or No Paramenter. How am I know suppose to use Element.SetParmeterByName. I also stoped working for Interger parameters.
Help?
[Element.SetParamenterByName]
Hello @scott.tomlinson - This has now been resolved for Revit 2023.1 and Dynamo 2.15, and will also be hot-fixed back to Revit 2023.0.1 along with a bunch of other bug fixes in Revit.
Unfortunately I cannot gives dates on this, but the hotfix should be coming out relatively soon fix the issue revit-191624 (#2826) by wangyangshi · Pull Request #2846 …
12 Likes
SeanP
August 5, 2022, 11:15pm
3
Noticed this in the release notes, and was happy to see it!
1 Like
Bummer on this one, but it seems there might still be an issue. Which is odd as it’s not what I saw after I ran the update.
We’re looking into a proper fix now - it appears, as Gavin mentioned above, to be an installer build issue. We’re working on properly identifying how to resolve this issue WARNING: Dangerous approach to use at your own risk below... If you want to be adventurous and live on the edge, you can replace the DynamoNodes.dll attached here inside your DynamoRevit installer.
This comes with a few caveats:
We take no responsibility for any problems that occur should you choose to take this acti…
The Element.SetParameterByName Code Block dosn’t work in my case also.
apd
September 4, 2022, 3:05pm
6
@john_pierson its still not working for me… Laterst verions installed.
Hi All
I am contemplating installing the hotfix.
1 Like
SeanP
October 17, 2022, 11:30am
8
Personally haven’t seen any issues with Dynamo.
2 Likes
Thanks! I’ll just take the leap and see.
So, I wanted to come back and update this thread and say… It appears that Revit 2023.1 (2023.1.1) has fixed this issue (finally).
Hoping everyone can get this fix this time around.
Side Note: This is a prime example of why having Dynamo included in Revit (with no ability to update), is actually causing more problems. Unless you replaced DLLs as recommended in another post, you would have been stuck with the MeasurableSpec bugs since Revit 2023’s initial release.
4 Likes
Hello, by installing this one the version of dynamo went from 2.13 to 2.16.1
delighted to finally be able to pin the notes on the nodes (see your video on blog)
Cordially
1 Like
