PR: TypeName parameter vs. Type Name builtIn
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
### Problem Description
... I have been successful with creating User Defined Property Sets over many years. But now somthing is not working. I can not assign the Type Name of Curtain Wall Panels (Door Component) to my User Defined Pset. This is the mapping details:
PropertySet: Pset_KK I IfcElement, IfcElementType
Type Text Type Name
FollowUp
I found the error in the Family, there was added a parameter in the family called TypeName, although it is not completly the same as Type Name with space, it causes the exporter not to Export the builtIn Type Name to User Defined Property Sets.
### Revit Version
2024.3.x
### IFC for Revit Addon Version
24.3.2
### Windows Version
11 24H2
Contributor guide
Research direction
No source file or test is named. Reproduce the reported User Defined Property Set mapping in Revit 2024.3.x with IFC for Revit 24.3.2, focusing on the collision between the family parameter `TypeName` and the built-in `Type Name`. Done means the built-in Type Name is exported to the mapped property set despite that family parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100