Create an new Entity "in-Entity" only using the Keyboard

[B_Sp]

Hey,

I think in fact that db’s in Notion are the Type equivalents, here’s why:

• They can be customized with all the various Fields. Each app has a list of Fields they offer. I’d argue that Notion’s has some Fibery doesn’t, Fibery has some Notion doesn’t. Would be interesting to do a side-by-side at some point

• In Fibery, if you want to create an entity that has certain pre-determined fields, you create a “Type.” Then, if you want to get some of those fields to pre-populate, which is why I’d use a Template, you can use defaults, but just in a few of those fields, like State and Single-Select. That’s why I made the request here to get more default capability, with Multi-Select:

Add Default Value on Multi-Select Fields

Hi guys, The default value option on Single-Select fields… [Image 2020-08-10 at 4.06.24 AM.png] is a very nice feature. It allows you to determine if you would like a tag to get picked up by each new entry, or not. This is another feature absent in Notion! I could really use it in the Multi-select field. I was hoping that since Multi-Select is new (released in April per below) perhaps you simply haven’t gotten to its implementation? I use this default value extensively in single-selec…

However in Notion, you can create limitless templates within the DB. So if I have a db all set up with the Properties (as “Fields” are called in Notion) of my choosing, when I create the “default” Page in that db, I get an “Entity” equivalent of Fibery, with all the properties I created. But, I can also do stuff like pre-fill relations, set any field I like, etc. and get an even more useful Page pre-ready. Can I do this in Fibery?

I’m not sure why you think this:

@Oshyan

In other words they’re not fields/properties, they’re not actionable, calculable, relatable (except in the sense of unstructured backlinks, of course).

because when I experimented with Templates in Notion, I did all kinds of pre-linking that I can’t do in Fibery.

Case in point: I have a “task” Type in Fibery that can relate to a another Type that is “Business Function,” which is going to be things like “Sales,” “Marketing” etc. If I want to quickly create a task linked to “sales,” I can’t do that from the “quick create” ctrl + K dialogue. I happen to have a sales guy and all his tasks should have that distinction. So I’ll have to create a whole new Type called “Sales Tasks” separate from my other Tasks if I want to handle this need. Of, force him to create all his tasks within the “Sales” Entity in my “Business Areas” Type, so no benefit of the “quick add” dialogue anymore.

In Notion, I create a db called “Tasks” and replicate basically the same Fields as my “Task” Type in Fibery. But, I then create a template called “Sales Task.” I can then add a pre-set relation to my “Sales” Business Functions db. Notion will let me with the “+” create that task in about two clicks. I cannot do this in Fibery.

My point with all this is I’m trying to illustrate what I think are some flows that we could easily get here in Fibery to actually leverage its superior underlying architecture to Notion. In this example, Notion won’t let me build out my “Business Function” db with various layers like in Fibery I can thanks to many-to-one relations. But I’m missing in Fibery as much flexibility, which might be funny to be writing, but I think it’s true, than I have in Notion in this particular case.

Cheers and thanks for the good dialogue! Hope somebody is reading this and it will all positively affect the Fibery roadmap!