# The luxury problem

**URL:** <https://community.fibery.io/t/the-luxury-problem/1073>\
**Category:** Get Help\
**Created:** [October 15, 2020, 8:05am UTC](https://community.fibery.io/t/the-luxury-problem/1073 "2020-10-15T08:05:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Haslien](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haslien/32/493_2.png) [@Haslien](https://community.fibery.io/u/Haslien)\
**Post date:** [October 15, 2020, 8:05am UTC](https://community.fibery.io/t/the-luxury-problem/1073/1 "2020-10-15T08:05:20Z")

</div>

Just wondering if any of you have noticed this.

When you have a single source of truth that you efficiently re-use everywhere through referencing, at some point you end up not really _writing_ new entries, but rather just create new entities containing references.

At this point, the one “mandatory” field `Name` becomes virtually useless and actually just cause extra work to fill in?

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [October 15, 2020, 12:13pm UTC](https://community.fibery.io/t/the-luxury-problem/1073/2 "2020-10-15T12:13:55Z")

</div>

Soon you will be able generate name automatically using a formula. We are working on that. (If I got the problem right)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 15, 2020, 2:44pm UTC](https://community.fibery.io/t/the-luxury-problem/1073/3 "2020-10-15T14:44:27Z")

</div>

Indeed, I often encounter a situation where all the meaning of an entity is contained in its relations and some non-text fields, and therefore yes, the Name field is redundant.  
As an example, for the test management app that I developed, I have a type called Test Execution, which is a record of: when a Test Case was executed, by whom, the step results and the overall outcome (pass/fail). There is no sense giving it a ‘name’ per se, but because the name field is the handle for other entities to refer to, it ends up being a sort-of summary of all the other fields/relations, e.g. “Test Case #1, 2020-10-13, Pass”  
Off course, the auto name option that Michael has said is coming is the nicest solution 🙂