# IfcBuiltElement USERDEFINED

**URL:** <https://forums.buildingsmart.org/t/ifcbuiltelement-userdefined/3127>\
**Category:** IFC\
**Tags:** ifc4\
**Created:** [November 15, 2020, 9:47am UTC](https://forums.buildingsmart.org/t/ifcbuiltelement-userdefined/3127 "2020-11-15T09:47:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![daviddelven](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/daviddelven/32/2384_2.png) [@daviddelven](https://forums.buildingsmart.org/u/daviddelven)\
**Post date:** [November 15, 2020, 9:47am UTC](https://forums.buildingsmart.org/t/ifcbuiltelement-userdefined/3127/1 "2020-11-15T09:47:50Z")

</div>

Hello,

Since IfcBuiltElement can also be instantiated in IFC4 RC2, I wonder why there is no “IfcBuiltElementTypeEnum” class. We will need to assign custom values to the ObjectType attribute for those especial elements without Schema entity correspondence.

Thanks

---

<div class="post-metadata">

**Author:** ![Moult](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/moult/32/196_2.png) [@Moult](https://forums.buildingsmart.org/u/Moult)\
**Post date:** [November 15, 2020, 11:24am UTC](https://forums.buildingsmart.org/t/ifcbuiltelement-userdefined/3127/2 "2020-11-15T11:24:03Z")

</div>

+1. This makes complete sense.

---

<div class="post-metadata">

**Author:** ![RacheleAB](https://avatars.discourse-cdn.com/v4/letter/r/c77e96/32.png) [@RacheleAB](https://forums.buildingsmart.org/u/RacheleAB)\
**Post date:** [November 18, 2020, 9:53am UTC](https://forums.buildingsmart.org/t/ifcbuiltelement-userdefined/3127/3 "2020-11-18T09:53:32Z")

</div>

it makes sense… till people won’t use it as the unique easy way to classify facility components