# Possible bug with adding a "Block" field to a model

**URL:** https://forum.builder.io/t/possible-bug-with-adding-a-block-field-to-a-model/1978
**Category:** Bugs
**Created:** [March 30, 2022, 6:02pm UTC](https://forum.builder.io/t/possible-bug-with-adding-a-block-field-to-a-model/1978 "2022-03-30T18:02:48Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ancheetah](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/ancheetah/32/751_2.png) [@ancheetah](https://forum.builder.io/u/ancheetah)
#### Post date: [March 31, 2022, 6:23pm UTC](https://forum.builder.io/t/possible-bug-with-adding-a-block-field-to-a-model/1978/2 "2022-03-31T18:23:02Z")

</div>

Hi @Canuckaholic, that type is undocumented and still in beta. Can you please explain your use case for it? One of the other common types should work for most situations. Thanks!

> [@Custom targeting attributes](https://forum.builder.io/t/custom-targeting-attributes/1757/4):
>
> Hi @prasad, while these types are still in beta and not officially documented yet, here is what I’ve found testing them out myself. The custom attribute types provide a more friendly user interface to input your targeting values in the Visual Editor as you have shared in your screenshot above. The “code” and “tag” types currently work well for targeting while the other DOM and Block types still require more testing. Once set in Builder “code” and “tag” values can be targeted off of in React jus…

---

_[View the full topic](https://forum.builder.io/t/possible-bug-with-adding-a-block-field-to-a-model/1978)._