# References to Views as a way to emulate Embedded Db's in Notion

**URL:** <https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247>\
**Category:** Ideas & Features\
**Created:** [December 16, 2020, 7:35pm UTC](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247 "2020-12-16T19:35:40Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [April 27, 2021, 8:15pm UTC](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247/11 "2021-04-27T20:15:15Z")

</div>

Thanks for that!

Re: references to Views: Yes, we frequently refer to views, if I want to talk about my Epics in a Meeting, I’ll reference the table for “Epics.” Views are the only way to reference an entire Type right now - those same Epics are in fact a Type, but there is no way to reference them now.

And re: commenting on Views, yes that would be a great starting point to solve the issue of how to document updates to them. This is even more important in the case of Types. Would really love to be able to comment freely on a Type to document what’s been going on with them. This would be a great way to avoid this issue:

> [@\[✔️DONE\] Admin activity history/audit log](https://community.fibery.io/t/done-admin-activity-history-audit-log/1148/8):
>
> Haha, so true. I use Airtable as well as fibery, and I often have to create rollups, lookups or formulas to achieve what I want. Sometimes I figure out a different / better way of doing something, but I’m paranoid about deleting old fields, because I’m not 100% sure that the field is actually redundant! I fear that if I’m not careful, the same will soon happen with fibery.

For example, if I want to simply add a new Status to a Type. How do I document what I did to my team? I could use a completely other, new Type I might set up just for this purpose called “Documentation,” and write a new Entity saying “In this Type, I added the new State of “Deployed” to go alongside the state of “Done” to show the absolutely final state of this work” etc. That workaround would be completely unnecessary if could comment in Types, just like in Wikipedia as you suggest this is model after.

Thanks!

---

_[View the full topic](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247)._