# \[DONE\] Copy-pasting an entity UUID to the whiteboard should add a card for it

**URL:** <https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477>\
**Category:** Ideas & Features\
**Tags:** whiteboard\
**Created:** [August 4, 2024, 5:03pm UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477 "2024-08-04T17:03:06Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\
**Post date:** [August 4, 2024, 5:03pm UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477/1 "2024-08-04T17:03:06Z")

</div>

There should be an easy way to add an entity to a whiteboard.  
Ideally there could be a form of drag and drop (of an entity from a view to the whiteboard) but I understand that might be quite hard to implement.  
A quick win IMO that would address the same issue would be to simply be able to copy the UUID of an entity and then pasting that in the whiteboard should create a card for said entity.

 ![shot_240804_195851](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d6018f0a43c5757759863aa2a4712ba13599b0e8.png)

by comparison, here is how Miro parses a link to a Jira ticket

 ![shot_240804_200722](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/59385195ec604ee8cfc20724beaa6e1e7a927d14.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:** [August 4, 2024, 5:30pm UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477/2 "2024-08-04T17:30:44Z")

</div>

Worth mentioning that a UUID is only guaranteed unique within a db, so it would be difficult to use it to create a whiteboard card.  
Perhaps, copying the entity view url would work as an alternative…

---

<div class="post-metadata">

**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\
**Post date:** [August 4, 2024, 7:04pm UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477/3 "2024-08-04T19:04:31Z")

</div>

Yes. Since the entity url is what gets pasted anyway and not the uuid itself, plus the url path is basically `space\database\name-uuid` I would assume this would work in pretty much all scenarios.

And even if it only worked in 99% of the cases due to some unforseen exception, it would still provide tremendous value as opposed to the current “search entity by name to add the card” approach.

---

<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:** [August 5, 2024, 5:11am UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477/4 "2024-08-05T05:11:49Z")

</div>

We’ve implemented it with a link to an entity, I hope we will include it into the next release

![2024-08-05 08.10.53](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3247a5ea9d654a9001aa6d799345e507c23928bb.gif)

---

<div class="post-metadata">

**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\
**Post date:** [August 5, 2024, 9:29am UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477/5 "2024-08-05T09:29:47Z")

</div>

That’s amazing. Thanks a lot  
Can’t wait for it

---

<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:** [August 5, 2024, 3:22pm UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477/6 "2024-08-05T15:22:10Z")

</div>

> [@Mircea\_Braescu](#):
>
> Can’t wait for it

This Thursday I hope 🙂

---

<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:** [August 8, 2024, 12:50pm UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477/7 "2024-08-08T12:50:13Z")

</div>

Released

> [@August 8, 2024 / octopus Multiple Entity Views, Group notifications by entity, and moooore](https://community.fibery.io/t/august-8-2024-multiple-entity-views-group-notifications-by-entity-and-moooore/6486):
>
> octopus Multiple Entity Views (Pro plan only) Multiple Entity Views allow users to create and manage multiple layouts for any database entity. For example, you can configure several Entity Views to display Feature entity differently: NOTE: Multiple Entity Views are available in Pro and Enterprise plans only moneybag. What problems it solves? Sometimes database can be large with dozens of even hundreds of fields, and different users in different context might want to work with some su…

---

<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:** [August 9, 2024, 8:27am UTC](https://community.fibery.io/t/done-copy-pasting-an-entity-uuid-to-the-whiteboard-should-add-a-card-for-it/6477/8 "2024-08-09T08:27:00Z")

</div>


