Hi All,
I was using my script to add shared parameter without any issue in Revit 2022. however, in Revit 2024 I have an issue as the API has been changed and I can’t add any shared parameter to “Other” anymore.
I tried to add the parameters to different group “PG_General” and it works fine as below.
but when I trying to Add these to “Invalid” it gives me this error.
I read that Autodesk changed the builtin parameter group for 2024 onwardshttps://forums.autodesk.com/t5/revit-api-forum/revit-2024-other-parameter-group/td-p/12086226 https://thebuildingcoder.typepad.com/blog/2023/11/journal-magic-adjacent-rooms-and-room-boundary.html#5
Is there any specific node should I use to select “other” as a group type?
Thanks
You can look at it as old school (Enums) vs new school (ForgeTypeId), but firstly lets get to those drop downs - Type of Parameter is a SpecTypeId, Group parameter under is a BuiltInParameterGroup. Old school is a bit hacky, new school has LabelUtils, ParameterUtils and UnitUtils. Revit is moving to ForgeTypeId for a lot of properties so now is probably a good time to lean in. Too much code to drop here - see the attached dyn file
[get_all_2023-11-20_09-16-35]
Get_All_Info_R24.dyn (12.0 KB)
This might help you out a bit!
1 Like
Thanks @rajeshjamariya16 it’s very helpful.
I will try to find the replacement of “Other” Parameter group.
To add to this I can see forgetypeIds are going to be on my radar so I bit the bullet and figured out how to get specs/groups by name. Much easier than I thought, I quite like them now vs the old method - targeting the human friendly name is great.
# Boilerplate text
import clr
clr.AddReference("RevitServices")
import RevitServices
from RevitServices.Persistence import DocumentManager
clr.AddReference("RevitAPI")
import Autodesk
from Autodesk.Revit.DB import *
# Current doc/app/ui
doc = Do…
OR I believe this actually what you’re looking for.
Hi @Mahmoud.ElNahas.PT
I don’t have the orchid package , but instead "INVALID" try an empty string ""
Hi @c.poupin I tried it with as " " or “” but the same error.
it strange as the archi-lab.net package can still extract it as “Invalid” but I can’t find a way to translate it as per the new 2024 enumerations
@Mahmoud.ElNahas.PT
I suggest you create an issue in the GitHub repo
