# Type Relationship Flexibility Enhancement

**URL:** <https://community.fibery.io/t/type-relationship-flexibility-enhancement/1115>\
**Category:** Ideas & Features\
**Created:** [October 30, 2020, 9:26am UTC](https://community.fibery.io/t/type-relationship-flexibility-enhancement/1115 "2020-10-30T09:26:12Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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 30, 2020, 11:24am UTC](https://community.fibery.io/t/type-relationship-flexibility-enhancement/1115/6 "2020-10-30T11:24:27Z")

</div>

I don’t know if this is what @NicolSpies was thinking about, but to answer the question as to

> [@mdubakov](#):
>
> the benefits you might get if we allow to define other fields as Primary Key

then I can see that being able to use a field other than the Name field as the ‘primary key’ allows a user to see different information in places where currently only the name shows (e.g. when using search or when trying to find the correct entity to link to in a relation).  
As a concrete example, the issue recently discussed:

> [@\[✔️ DONE\] The Release Issue](https://community.fibery.io/t/the-release-issue/832):
>
> We have a relation like product \<-\> release(s) product installation \<-\> release … But the issue is a release is a product related thing (every product has its own release numbers) as it must be possible to see which changes for a product are in a release. And now when selecting the release from a dropdown, it only shows e.g. “1.4.0” but no product information. Has someone an idea how to create real product related releases (but not an new model for each of them) or filter them in dropdowns …

The user could create a formula field that concatenates Product + Release and then define this as the ‘primary key’.  
Of course, this particular problem will be solved when the Name field can contain a formula (which I know is in the works) but I can imagine other similar scenarios.  
FWIW I think Coda allows the user to choose which field is the display name for an entity, so I guess they think this is useful for some of their users.

As I said though, I don’t know if this is what the original question related to, since I have no real idea what is referred to when saying

> [@NicolSpies](#):
>
> existing relational design techniques and methods

---

_[View the full topic](https://community.fibery.io/t/type-relationship-flexibility-enhancement/1115)._