You may have noticed over the years that the naming of property sets in Revit has changed from version to version.
For example, in a model exported from Revit Architecture 2011, the property “OmniClass Number” is located in the “PSet_Revit_Type_Identity Data” property set.
However, when this model is upgraded in Revit 2017, and exported with the out-of-the-box IFC exporter, the property is found under “Identity Data.”
When the IFC Exporter is updated to one of the latest on https://sourceforge.net/projects/ifcexporter/files/2017/, the property is then found under “Identity Data(Type).”
This can cause issues with your rulesets. For example, the rule below checks to ensure the “OmniClass Number” property is defined for all doors. Notice it is looking for the property under “Identity Data.”
All doors do have this property defined in each version of the model; however, in the screenshot below, you can see that this rule fails for all doors exported from Revit Architecture 2011 and Revit 2017 with the IFC Exporter v17.3 installed.
If you have a mixture of models from different versions of Revit, you can work around the issue by using classification. More information on classifications can be found here:
Create a classification for the OmniClass property:
Add columns for the various property set names of the property:
Set the classification to the value of whatever property location has a value defined by using “*?” wildcards characters in the property columns and “=[column number]” in the Classification Name column:
Change the property column in the rule the to use the classification of the property:
Instead of the “Property Sets” property group, select “Classification” to use your classification of the property.
After running the check with the modified version of the rule, this rule passes since all doors do have an OmniClass Number defined.