Dirk Van Rillaer

2020.2.0.48 is the version number of the Revit update 2020.2 and it refers to the out-of-the-box exporter, which is outdated (although its higher number). The exporter version 2020.1.0.1 is the current/latest exporter (unless you built your own solution than you can have a slightly more up-to-date version).

Hi Anno, To my surprise, it is indeed possible to use such a combination expression. I tried successfully the following notation as expression for a Wall/Door/Roof {$this("Base Constraint").("Name")+$this("Level").("Name")+$this("Base Level").("Name")} so in the same style all the other "leveltypes" could be added to this expression. Regards, Dirk

Hi Hans, As far as I know, the only way to get rid of the prefix, is by using an expression. In this case the expression would be: {$this("Base Constraint").("Name")} Regards, Dirk

Many thx for the script! I will give it a try.

Not that I know ... unfortunately. I suppose the only solution would be if something in the code of the exporter would be altered concerning the evaluation of empty fields. @angelvelezsosa: could you shine some light on this?

Hi Adrian, There is a difference between an empty field and an untouched empty field. Only the untouched ones are skipped by export. If you fill in a value for the parameter Reference Level / apply / delete value / apply, and then export it to IFC, you will notice that also the Reference Level parameter is exported. Regards, Dirk

Hi Milutin, You can assign the parameter IfcSpatialContainer as Instance parameter to any object. Suppose, you have a Revit Level with Name "Level 2", which is ticked as Building Story. You have to use the Revit level name as value (not the name of an override for IFC export, which is for instance "02"):. So, if you use IfcSpatialContainer = Level 2 it will be exported to the desired IfcBuildingStorey "02" Regards, Dirk

you're welcome!