# Button to add entity of the same database as current entity

**URL:** <https://community.fibery.io/t/button-to-add-entity-of-the-same-database-as-current-entity/10204>\
**Category:** Ideas & Features\
**Created:** [December 23, 2025, 9:30am UTC](https://community.fibery.io/t/button-to-add-entity-of-the-same-database-as-current-entity/10204 "2025-12-23T09:30:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [December 23, 2025, 9:30am UTC](https://community.fibery.io/t/button-to-add-entity-of-the-same-database-as-current-entity/10204/1 "2025-12-23T09:30:22Z")

</div>

Adding a new entity of the same database is a very frequent action that is currently not easy to do.

 ![msedge_A7X6OG9bMU](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b026549cb358ffcc97a587a6def4887f659e1150.png)

---

<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:** [December 23, 2025, 9:48am UTC](https://community.fibery.io/t/button-to-add-entity-of-the-same-database-as-current-entity/10204/2 "2025-12-23T09:48:45Z")

</div>

You can add a button to do this yourself:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/ad7b94b3ed613db58880ce2c4490e1f086ce9b14.png)

(although it won’t be positioned where you have shown)

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [December 23, 2025, 2:14pm UTC](https://community.fibery.io/t/button-to-add-entity-of-the-same-database-as-current-entity/10204/3 "2025-12-23T14:14:44Z")

</div>

Yes, but there are two challenges around creating a button:

- This need appears throughout my use of many databases. That would require many button automations. Unless a button can trigger the database of the currently viewed entity view.
- The location at the top is indeed ideal. Hopefully in the future entity views become like dasboards where we can put fields above the Name, or better, the Name becomes a regular field. (Mabye also when entity view Hero section fields are implemented, which would allow to create consumer friendly entity views)