Editing Revit setup for OpenBIM/Revit IFC type products

The following attributes may be filled.

Note that the shared parameter names used for these parameters, such as <code>Ifcname</code>, are ''not'' in CapsCase format. This is because Revit only allows you to create parameters either as a type or instance parameter, but not both. As the parameter names are hardcoded in the Revit IFC exporter, we have established a convention of using CapsCase for instance parameters, and Capitalised for type parameters.

{| class="wikitable"
! '''Attribute Name'''
! '''Required'''
! '''Procedure'''
|-
| <code>Name</code>
| Yes
| By default, Revit exports the family's <code>Type Name</code> value. If these values match the codes used in schedules and annotation tags, your <code>Name</code> attribute will be correctly filled. In the likely event that this isn't the case (e.g. you are tagging a <code>Type Mark</code> field or other custom parameter), you will need to create a new <code>Ifcname</code> type parameter, assigned to the object.
|-
| <code>Description</code>
| Yes
| Create a new <code>Ifcdescription</code> type parameter, assigned to the object.
|}
@@ Line 1: / Line 1: @@
-{{Autodesk_Revit}}
 The following attributes may be filled.
-Note that the shared parameter names used for these parameters, such as <code>IfcName[Type]</code>, need to have <code>[Type]</code> as a suffix. It may be required to update to the latest IFC exporter, as the one shipped by Revit has a bug where type attributes are ignored.
+Note that the shared parameter names used for these parameters, such as <code>Ifcname</code>, are ''not'' in CapsCase format. This is because Revit only allows you to create parameters either as a type or instance parameter, but not both. As the parameter names are hardcoded in the Revit IFC exporter, we have established a convention of using CapsCase for instance parameters, and Capitalised for type parameters.
 {| class="wikitable"
@@ Line 11: / Line 10: @@
 | <code>Name</code>
 | Yes
-| By default, Revit exports the family's type joined with the <code>Type Name</code> value (e.g. <code>Basic Wall:Block Wall - 140</code>). If you enable the <code>Use Type name only for IFCType name</code> option in the export <code>Advanced</code> settings tab, this will be simplified to just the type name (e.g. <code>Block Wall - 140</code>). The IFC requirement is to fill in the <code>Name</code> attribute with the codes used in schedules and annotation tags (e.g. <code>BLK140</code>). In the likely event that this isn't the case (e.g. you are tagging a <code>Type Mark</code> field or other custom parameter), you will need to create a new <code>IfcName[Type]</code> type parameter, assigned to the object, and tag that in your drawings instead of <code>Type Mark</code> or otherwise.
+| By default, Revit exports the family's <code>Type Name</code> value. If these values match the codes used in schedules and annotation tags, your <code>Name</code> attribute will be correctly filled. In the likely event that this isn't the case (e.g. you are tagging a <code>Type Mark</code> field or other custom parameter), you will need to create a new <code>Ifcname</code> type parameter, assigned to the object.
 |-
 | <code>Description</code>
-| Recommended
+| Yes
-| Create a new <code>IfcDescription[Type]</code> type parameter, assigned to the object.
+| Create a new <code>Ifcdescription</code> type parameter, assigned to the object.
-|-
-| <code>ApplicableOccurrence</code>
-|
-| It seems not possible to assign this, despite the <code>IfcApplicableOccurrence[Type]</code> shared parameter being distributed by Autodesk.
-|-
-| <code>ElementType</code>
-|
-| Create a new <code>IfcElementType[Type]</code> type parameter, assigned to the object.
-|-
-| <code>PredefinedType</code>
-| Recommended
-| Create a new <code>IfcExportType[Type]</code> type parameter, assigned to the object. The value is case insensitive.
 |}
-[[Category:Autodesk Revit]]