reststicky.blogg.se - Configure simultaneous processes coda 2

instead of one table for all stages and multiple views within that table.

You have a table for each stage in a process.

Are you creating tables for different people just to keep them separate?.

Are you often trying to get an overview by combining multiple tables that track similar things?.

Do you notice that some tables are very similar in structure?.

Do you often find yourself copying and pasting tables, or copying and pasting records from one table to another?.

If the following sounds like you, you should consider taking your records from multiple tables, putting them together into one table, and then using views to see just the information you need for the task at hand. Recognizing the patternĬheck the following to see if your base might benefit from some redesign. Read on to find out if your own base has too many tables.

If you represent status changes by moving a record from one table to another, it can be easy to make mistakes while copying and pasting multiple tables for the same types of items can also make it difficult to summarize findings from all of your items at a high level.

While this can make finding what you need easier in the short term, it can also present problems in the long term. It might be to represent different statuses (separate tables for Blog post ideas, Posts in progress, and Completed posts) or subtypes (separate tables for Rap artists and Country artists). Sometimes, beginners to Airtable might create multiple tables for the same type of item. For example, a table could be a list of blog posts or recording artists on your record label. In general, you can think of a table as a list containing all the people, ideas, or items of a specific type.