# Provide Context for Duplicate Names

**URL:** https://community.fibery.io/t/provide-context-for-duplicate-names/1534
**Category:** Ideas & Features
**Created:** [April 7, 2021, 1:42pm UTC](https://community.fibery.io/t/provide-context-for-duplicate-names/1534 "2021-04-07T13:42:46Z")
**Posts on this page:** 1
**Showing post:** 10

<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: [April 12, 2021, 12:48pm UTC](https://community.fibery.io/t/provide-context-for-duplicate-names/1534/10 "2021-04-12T12:48:20Z")

</div>

Just so I understand, do you mean that Types could be included in the search box **as search results** and if a user chooses the Type, he/she gets returned the default list of all the Entities of that Type?  
It sounds almost as though you’re advocating for the default table view to be persistent/locked (can’t be deleted, have filters applied etc.) and for it to move with the Type if that gets moved to a different App. Am I right?

Or do you mean a jump list as was discussed here, that wouldn’t actually take up any space in the side bar?

> [@Mention or links to types](https://community.fibery.io/t/mention-or-links-to-types/924):
>
> Can we please have the ability to mention/link to a type (rather than just linking to an entity or a specific view)? Sometimes, I want to write an explanation of how to use an app, and want to mention a type, rather than a single instance or a specific table/board. It might link nicely with some of the issues discussed here:

---

_[View the full topic](https://community.fibery.io/t/provide-context-for-duplicate-names/1534)._