Autodesk / Autodesk/revit-ifc

PR: Psets with IFCElement are not exported, exports only as IFCRoot

Open
#879 1 comment 0 reactions 0 assignees View on GitHub
problem
Dominant language
C#
Stars
637
Forks
225
PR merge metrics
No merged PRs in 30d

Description

### Problem Description

I encountered an issue while trying to export classification parameters from a custom user-defined property set in Revit. In my .txt PSet file, I had specified the instance as IFCElement, but the parameters were not being exported to the IFC file—regardless of the Revit version I used (2022, 2023, 2024, or 2025).

After some troubleshooting, I compared it with a different .txt PSet file where the instance was defined as IFCRoot. I updated my original file to use IFCRoot instead of IFCElement, and the export worked as expected.

So if you run into a similar issue with parameters not exporting, make sure to check whether IFCRoot might be the correct instance to use instead of IFCElement.

![Image](https://github.com/user-attachments/assets/6ac83766-cede-4409-8191-a604f59f7644)

### Revit Version

2025.4.x

### IFC for Revit Addon Version

25.4.0

### Windows Version

11 24H2

Contributor guide

Open the contributing guide

Research direction

Reproduce the export with the reported Revit 2025.4.x and IFC for Revit 25.4.0 versions, using a custom .txt property set with the instance set to IFCElement. Compare the resulting IFC output with the same property set configured as IFCRoot; no source file or test entry point is identified, so completion would require defining the expected IFCElement behavior and adding a regression check.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.