Autodesk / Autodesk/revit-ifc

INQ: Issue in "Export As IFC Entity"

Open
#967 4 comments 0 reactions 0 assignees View on GitHub
inquiry
Dominant language
C#
Stars
637
Forks
225
PR merge metrics
No merged PRs in 30d

Description

### Inquiry description

Hello,

in Revit 2026, the “Export As IFC Entity” interface does not correctly preserve the spelling of all PredefinedTypes under the IfcEntity “IfcFootingType”.
As you can see, it should remain written as a single word, but it is separated by an underscore during the export.
This leads to errors when these values are validated.

Is the same in Revit 2024...

Image

### Revit Version

2026.4.x

### IFC for Revit Addon Version

26.4.1

### Windows Version

11 25H2

Contributor guide

Open the contributing guide

Research direction

Reproduce the “Export As IFC Entity” workflow in Revit 2026.4.x and, if possible, Revit 2024, focusing on the IfcFootingType PredefinedType value. Confirm that export preserves the single-word spelling rather than inserting an underscore, and validate the exported value against the expected IFC spelling.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.