Skip to content

Tables & records

Every database is built from two simple ideas: fields (the columns that define what each item has) and entries (the rows that hold the actual data). Once those two clicks into place, the rest is easy. This page walks through creating a database, shaping its columns, and filling it with data.

  • A field (also called an attribute or column) is a named, typed slot — for example “Company Name” (text), “Deal Size” (money), or “Stage” (a dropdown). Fields are the same for every row.
  • An entry (also called a record or row) is one item — one lead, one product, one calendar slot. It holds one value per field.

That’s the whole model. A database is just a set of fields, plus all the entries that fill them in.

  1. Open Databases from the main navigation.
  2. Click Create database.
  3. Give it a clear name — “Sales Leads”, “Inventory”, “Content Calendar”.

You now have an empty table, ready for columns.

Add a column for each thing you want to record about every item:

  1. Click Add field (add attribute).
  2. Choose a type — Text, Number, Date, Money, a dropdown of choices, a file, and more. The full list is in Field types.
  3. Name it, and set any options the type offers (currency for money, the list of choices for a dropdown).
  1. Click + to add a new row.
  2. Fill in each cell — type into text, pick from a dropdown, choose a date, drag a file into an attachment field.
  3. Edits save automatically as you move from cell to cell.

Mark a field required when an entry doesn’t make sense without it (a lead with no name, say). BridgeApp won’t let a row be saved with a required field left empty.

Any field can be set to array — meaning a single cell can hold more than one value. An “Attachments” field set to array lets one row carry several files; a “Tags” dropdown set to array lets you pick several tags. Use it whenever “this item can have many of these” is true.

Already have your data in a spreadsheet? Import a CSV to create many entries at once. BridgeApp checks the incoming data against your field types and required-field rules as it imports, so what lands in the table is clean.