Autodesk
PR: Many import class mappings seem to be hardcoded
Problem Description
As the issue title states: Many of the import class mappings seem to be hardcoded. When linking MEP models we would like to be able to better map the IFC classes to Revit categories. Example froma recent model: IfcAlarmType, IfcElectricTimeControlType and IfcOutletType all map to Generic Model despite our import class mapping table containing different target categories for these classes. Since all elements are converted to DirectShapes in any case during the linking process hwy does the target category need to be hardcoded?
Revit Version
2024.0.x
IFC for Revit Addon Version
24.x.x
Windows Version
10 22H2
Is this really a Revit 2024 issue or a Revit 2025 issue? There was a regression in functionality for the mapping table for link IFC which I believe has already been corrected; I will verify.
I believe this is fixed in Revit 2025.1 - do you have access to that to check?
The issue is reproducible in Revit 25.1.0.9 (20240401_1515) with IFC plugin version 25.0.0.393 but is no longer present in Revit 25.1.0.15 (20240408_1515) with the same IFC plugin version.
Conclusion: The problem appears to have been resolved in Revit 25.1.0.15. Users experiencing this issue should update to the latest available version.
There were some regressions around category mapping that, if critical, can be resolved by using the legacy link IFC version.