ENH: Disable Uniformat classification if Assembly Code parameter is used for other classification system
Enhancement Description
Context
The Uniformat classification system isn't relevant in all markets - because they have their own classification systems. But the Revit user interface for assigning the Assembly Code parameter is really useful and it therefore makes sense to use it for whichever classification system is required for a given project. And yes, we are aware we could use the ClassificationCode shared parameter option and the Standardized Data Tool (aka Classification Manager). But using the Assembly Code parameter with a custom classification text file is - in our opinion - the best choice in terms of UX and ease of deployment.
The problem
If we use the Assembly Code parameter as our classification parameter in our export settings, like so:
it kinda works, but not entirely:
Proposed change
If the Assembly Code is picked as a classification parameter in the IFC export settings:
- Do not export a Uniformat classification (also asked for in #486)
- Use the Assembly Code Description parameter as the classification name
If not, assume it's Uniformat and carry on as usual.
Revit Version
2025.4.x
IFC for Revit Addon Version
25.4.0
Windows Version
11 24H2
Hello @andydandy74,
This is a confirmed enhancement request that has been addressed in recent development. The behavior described is no longer reproducible in the latest versions of the IFC exporter.
We consider this issue resolved. If you encounter similar problems in the future with a different workflow, please feel free to open a new ticket.
Thank you for your contribution to improving the IFC exporter!
Testing environment:
- Autodesk Revit 2023 (IFC 23.4.1.0)
- Autodesk Revit 2024 (IFC 24.3.30.11)
- Autodesk Revit 2025 (IFC 25.4.3.0)
- Autodesk Revit 2026 (IFC 26.3.0.0)
@ArtemHnatko That is great news. :-) However, after running a quick test, these are my findings:
25.4.0 using ENU as UI language:
- Using the English parameter name for Assembly Code ("Assembly Code") ✅
25.4.0 using DEU as UI language:
- Using the German parameter name for Assembly Code ("Baugruppenkennzeichen") ❌
- Using the English parameter name for Assembly Code ("Assembly Code") ❌
- Using the API parameter name for Assembly Code ("UNIFORMAT_CODE") ❌
It may be different in other versions, but my suspicion after this quick test is that this improvement has not been implemented with the topic of localization in mind.