# Field type Reference

**URL:** <https://community.datagerry.com/t/field-type-reference/100>\
**Category:** Feature Requests\
**Created:** [May 8, 2020, 9:10am UTC](https://community.datagerry.com/t/field-type-reference/100 "2020-05-08T09:10:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mbatz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/mbatz/32/5_2.png) [@mbatz](https://community.datagerry.com/u/mbatz)\
**Post date:** [May 19, 2020, 11:25am UTC](https://community.datagerry.com/t/field-type-reference/100/3 "2020-05-19T11:25:04Z")

</div>

Hi @marcinw

as far as I can see, your idea is related to [this topic](https://community.datagerry.com/t/thinking-of-a-n-field/72)? So instead of storing a single value for a field (which may also have another type than object-ref), a list of values should be stored. Would that help?

---

_[View the full topic](https://community.datagerry.com/t/field-type-reference/100)._