# Choose the field to show in an entity relation

**URL:** <https://community.fibery.io/t/choose-the-field-to-show-in-an-entity-relation/5207>\
**Category:** Ideas & Features\
**Created:** [September 27, 2023, 11:45am UTC](https://community.fibery.io/t/choose-the-field-to-show-in-an-entity-relation/5207 "2023-09-27T11:45:49Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![arthurpires](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/arthurpires/32/7815_2.png) [@arthurpires](https://community.fibery.io/u/arthurpires)\
**Post date:** [September 27, 2023, 11:45am UTC](https://community.fibery.io/t/choose-the-field-to-show-in-an-entity-relation/5207/1 "2023-09-27T11:45:49Z")

</div>

It would be nice to be able to select a specific field of an entity to display in a view.  
Imagine this scenario:

- I have a central Sprint entity that has a “team” relation
- When adding a Sprint to a Task entity I would like to display the name of the Sprint as a formula of:  
“Team - Sprint #XX”,

Or this scenario:

- I have the same ProductArea across applications: Authentication in MobileApp and Authentication in WebPlatform
- Currently I have two ProductAreas created
- When adding a ProductArea to a Task I would like to be able to see from which Application this ProductArea is from  
 ![Screenshot 2023-09-27 at 08.42.16](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/20e15a4a73f3b54825a44536c5e0ecf93b0a3496.png)

If there’s a better approach to any of this scenarios I’m happy to hear since I’m new to Fibery 🙂

---

<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:** [September 27, 2023, 12:27pm UTC](https://community.fibery.io/t/choose-the-field-to-show-in-an-entity-relation/5207/2 "2023-09-27T12:27:39Z")

</div>

Are you aware of [this](https://the.fibery.io/@public/User_Guide/Guide/Generate-Entity-Name-with-Formula-43)

---

<div class="post-metadata">

**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\
**Post date:** [September 27, 2023, 1:43pm UTC](https://community.fibery.io/t/choose-the-field-to-show-in-an-entity-relation/5207/3 "2023-09-27T13:43:10Z")

</div>

Hi @arthurpires, you can generate the names through a formula. So your Sprint can be named automatically “Team - Sprint XX”.

I use this a lot. Has it’s pros and cons. Main con is when creating new items of an entity with generated name, as it’s slower and more cumbersome.

---

<div class="post-metadata">

**Author:** ![arthurpires](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/arthurpires/32/7815_2.png) [@arthurpires](https://community.fibery.io/u/arthurpires)\
**Post date:** [September 27, 2023, 8:57pm UTC](https://community.fibery.io/t/choose-the-field-to-show-in-an-entity-relation/5207/4 "2023-09-27T20:57:06Z")

</div>

I was thinking about something more dynamic, like in a view I can show Name and Team, in another view only the Name is necessary

---

<div class="post-metadata">

**Author:** ![ccollins](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@ccollins](https://community.fibery.io/u/ccollins)\
**Post date:** [September 27, 2023, 9:15pm UTC](https://community.fibery.io/t/choose-the-field-to-show-in-an-entity-relation/5207/5 "2023-09-27T21:15:22Z")

</div>

> [@arthurpires](#):
>
> w I can show Name and Team, in another view only the Name is necessary

I very much agree with this. We use a lot of formula names but there are a lot of downsides. Ignoring the difficulty with creating entities w/ formula names (talked about in many other threads), another huge downside to formula names is that making entity names distinct naturally makes the name longer.

For example:

- Vendor-A works on a lot of my projects. The way my schema is setup, every time Vendor-A is assigned to a project, a sub-entity is created. “Project-A\_Vendor-A”, “Project-B\_Vendor-A”, etc. Having distinct sub-entities per project is very important to collect information about the vendor specific to that project. And on the original Vendor-A page, I can aggregate information across all their project pages.  
The problem, like @arthurpires noted, is that if I link their project page anywhere, the relation field says “Project-X\_Vendor-A”. It ends up being a very long title. And when the View I’m looking at is project filtered, the “Project-X” portion of their name is no longer relevant, it’s just taking up valuable space.
- But alternatively, if you take away that portion of their name in the formula, it makes it impossible to find them in search or a non-filtered relation list.

---

<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:** [September 28, 2023, 7:11am UTC](https://community.fibery.io/t/choose-the-field-to-show-in-an-entity-relation/5207/6 "2023-09-28T07:11:05Z")

</div>

For collection fields (to-many relations) you can choose which fields are visible.

Unfortunately, it isn’t yet possible to show fields from an item which is linked via a to-one field.
