Intro to Afterpattern database

Updated: January 28, 2021

Use an Afterpattern database (hereafter simply "database") to:

  • Organize and review data collected by your apps
  • Pull data into your apps to avoid re-entering the same data again and again
  • Share data with your portal users

Take a tour of databases:

Create a database

You can create a database directly from your Afterpattern dashboard:

Anatomy of a database

A database is a series of tables, and each table is a spreadsheet:

Each row (designated in blue above) is one "object" of data. Each column (designated in pink above) is an attribute within these objects.

For example, in a database table that contains client data, each row is one client. A "client" is a data object with attributes like 'name', 'date of birth', etc.

Each row must have at least one unique attribute. This is the key column:

Data types

Each column in your database has a datatype, e.g. plain text, number, true/false, etc. You can only populate a column with it's specified datatype (e.g. you can't add plain text to a true/false column). Once a column's datatype is chosen, it can't be changed.

Intro to relational data

One of the most powerful features is the ability to create relational tables.

Relational tables are 2+ tables that are linked together with "has many" or "belongs to" datatype columns. For example, you can have a table with client data that is linked to a table with data about each client's respective children:

Creating relational tables is easy, just add a "has many" or "belong to" datatype column to a table (this will prompt to select a second table to connect it to). Using relational data in your apps is a bit more advanced. This topic is covered in the relational data lesson.

Contact us for support

Talk to a real person, quickly. We're available 9am - 5pm EST.