Improvements in IFC export

Tekla Structures
Modified: 12 Feb 2025
2025
Tekla Structures

Improvements in IFC export

In Tekla Structures 2025, there are changes in the IFC property set configuration file location and in exporting the assembly UDAs.

Change in IFC property set configuration file location

The common\inp folder has been reorganized so that different kinds of content are stored in more specific folders.

The IFC property set configuration files have been moved from \common\inp to \common\collaboration\ifc. The XS_INP advanced option has been updated in teklastructures.ini. You can now use ready-made IFC property sets from the common environment without taking other settings from \common\inp so that you define \common\collaboration\ifc folder for the XS_INP advanced option in your own .ini file.

Assembly UDAs in IFC4 export

Previously, the user-defined attribute values that were inherited from the assembly main part were not written to assembly objects in the IFC4 export. This issue has now been fixed as follows: When you fetch the UDA from the assembly, and the UDA has no value or has the default value (like for RENOVATION_STATUS, the default value is an empty string), Tekla Structures tries to fetch the value from the assembly main part. If the assembly main part returns a valid value, it is used.

  • If the assembly value and the main part value are default values, the assembly value is used.
  • If the assembly does not have a value and the main part has a default value, the main part default value is used.

You can disable this functionality using the advanced option XSR_DISABLE_ASSEMBLY_UDA_INHERITANCE. If you set the advanced option to TRUE, and if UDA is not set on the assembly level, the UDA is left empty or it uses assembly level's default value. If you set it to FALSE, the UDA is inherited from the main part.

IFC subtypes in alphabetical order

The predefined IFC subtype list Subtype (IFC4) in the property pane is now sorted alphabetically.

Was this helpful?
Previous
Next