Databases and properties
How to make a database, add entries and set up its properties.
A database is a page that collects entries of the same shape. Each entry is a page too, so opening one gives you the same body, comments, version history and permissions as any page.
Making one
- Press + New (새로 만들기) under the private pages list in the sidebar, or Add subpage (하위 페이지 추가) in a page menu (⋯).
- Choose Database (데이터베이스) as the page type and press Create.
- In the empty database, add properties yourself with Edit properties (속성 편집), or press Start from a database template (데이터베이스 템플릿으로 시작) to fill it with ready-made properties, views and entry templates.
You can also pick a database template in the template gallery. To show a database inside another page, use a database view block.
Entries
- Add item (항목 추가) at the top makes a new entry. On a board, every group has its own New item.
- An entry added in a filtered view gets the values the filter asks for, so it does not vanish from that view.
- Clicking an entry opens it the way the view says. Choose Full page, Side panel or Center dialog under How to open items (항목 열기 방식) in the view settings.
- The ⋯ on a row or card opens, duplicates or moves an entry to the trash. In a table, tick several entries to move them to the trash together.
- The Search database button at the top quickly searches this database's titles and text properties only.
- Entries are kept out of the sidebar tree by default. Turn on Show entries in the sidebar in Page appearance if you need them there.
Properties
Edit properties (속성 편집) at the top opens a side panel. Add properties there, rename and reorder them, and delete them. The Name property that holds each entry's name can be renamed too (to Customer, say), but not deleted. On an entry's page it is the large title at the top, so the property list under it does not show it again. Picking a type for a new property says under it what that type is for, and hovering a listed property's type says the same. Reorder a property or an option by dragging the grip (⋮⋮) at its left, or with the arrow keys while the grip has focus. Database description holds a note on what the database collects. Editing properties needs Manage permission on the database.
Two properties of a database cannot share a name, nor two options of a property. Case and surrounding spaces are ignored. When names clash in an import, the later one gets a number (for example, Status 2).
| Property | Holds |
|---|---|
| Title | The entry's name |
| Text · Link · Number | Text, an address, a number. Numbers can be formatted as percent or currency, with set decimal places. |
| Checkbox | Yes or no |
| Date | One date or a range, optionally with a time |
| Select · Status · Multi-select | A choice from set options, each with a colour and an order |
| User | Space members. The people named see the entry in Assigned tasks and on Home, and are notified. |
| Files | Uploaded files and pictures, shown as thumbnails in a table |
| Relation | Links to entries of another database or of the same one |
| Place | A place name with its address and coordinates, used by the map view |
| Formula · Rollup | Values calculated from other properties |
| Created time · Last edited time · Created by | Automatic properties every database has |
Relations and rollups
- When making a Relation, pick the database to link to and whether an entry links to Multiple items or One item only.
- Set up a two-way relation pairs it with a relation property in the other database, so a link made on either side shows on both.
- A relation that points to the same database can have a role. Sub-items shows sub-items under their entry in a table; Dependencies joins schedules one after another on a timeline. Turn on automatic schedule shifting and later tasks move when a predecessor runs late.
- A Rollup gathers a property of the related entries and calculates with it: count, sum, average, minimum and maximum, earliest and latest date, percent checked and more. It needs a relation property first.
Formulas
A Formula property calculates a value from the entry's other properties. + Property and + Function in the editor insert names, and a mistake is pointed out by its character position.
Renaming a property that a formula reads puts the new name into the formula. Deleting a property that a formula or rollup uses names that formula or rollup in the confirmation. Once it is deleted, the column header and its cells show a ⚠ mark, with the reason on hover.
| Example | Result |
|---|---|
prop("Amount") * prop("Quantity") | The two numbers multiplied |
dateBetween(prop("Due"), today(), "days") | Days left until the due date |
prop("Tags").length() | How many tags are chosen |
Duplicating
In a database page's menu (⋯), Duplicate with rows (행까지 복제) or Duplicate structure only (구조만 복제) makes a copy beside the original, its name ending in (사본). They are Notion's "Duplicate with content" and "Duplicate without content". On a database page, Ctrl/Cmd+Alt+D is Duplicate with rows.
- Duplicate structure only copies the properties and their options, the shared views, the item templates with the default template, and the automations. Duplicate with rows adds the rows, with their bodies, attachments and values. A copied row's creator and created time are the person who duplicated it and that moment.
- A relation to the same database (sub-items, dependencies) links rows within the copy. A relation to another database becomes a one-way relation to that same database. Rollups and formulas are rebuilt to read the copy's properties.
- Automations and repeat schedules are copied switched off, so you turn them on yourself after checking them. Webhook actions are not copied, since each address has its own secret key. Automations are copied only when the person duplicating has Manage on the original database.
- Personal views, comments, version history, form publications and automation run history are not copied. Rows you cannot open are not copied either.
- Duplicate with rows takes up to 2,000 rows and 200 MB of attachments. Over that, Duplicate structure only is offered.
- A large database is copied a little at a time, so the server keeps serving everyone else, and the progress is shown meanwhile. The copy appears beside the original as soon as it starts and fills in until it is done; closing the window does not stop the duplicate.
- If a copy stops midway (a server fault or restart), a partly made copy is left beside the original. Pressing Continue (이어서 하기) fills it in. While the duplicate is still running, or within an hour of its start, choosing the same duplicate again goes on with that copy too. An older one may already be in use by someone, so choosing it again makes a new duplicate. Move a copy you do not need to the trash.
- The duplicate items show only to those who can make the copy. The copy goes under the same page as the original, so you must be able to manage that page; if the original is private, being able to edit it is enough. A database at the top of the Space can be duplicated by anyone but guests.
- The copy does not take the sharing given to the original; it follows the permissions of where it is. If the original is private (not following the page above it), the copy is made private to the person who duplicated it. Private rows are copied as private.
- If something could not be copied, a list of what was left out and why is shown before the copy opens.
- ⋯ → Duplicate on a document copies the databases under it the same way, rows included, and relations between them link their copies. Linked database views and mentions in the body point at the copies. If the whole copy holds more than 2,000 rows or 200 MB of attachments, those databases are copied as their structure only, and you are told so.
- The copy of a page or database at the top of a teamspace is made in that teamspace. So is a copy made from version history.
- The sub-pages inside rows, and the databases in them, are copied too. As with a document, a copy takes up to 50 sub-pages and 5 levels.
- When you duplicate a document, the databases under it come along only if you can manage the page the copy goes under; otherwise you are told they were left out. A private database is the exception: it is copied without that right, private to the person who duplicated it. Private sub-pages are copied as private, and mentions in the copied body notify nobody again.