3 Principles for Building Airtable Databases Like a Professional

The Key Principles:
1. Don’t repeat fields
2. Eliminate redundant work with linked records
3. Make good use of the primary field
⭐️ Part of a business or enterprise team?
Access my services - www.3rings.co
⭐️ Product Comparisons
Airtable vs Excel - • Airtable vs Excel and ...
Airtable vs Notion - • Is Airtable better tha...
⭐️ Airtable Basics
Airtable for Beginners - • Learn Airtable in 8 mi...
Linked Records - • Understanding Airtable...
How Dates Work - • How Dates Work in Airt...
Sign up for Airtable with my affiliate link (thank you!) - airtable.com/invite/r/R3UWDio5
To Do List Template - www.3rings.co/resource/list-e...
Inventory Template - www.3rings.co/resource/clothi...
Expense Reimbursements Template - www.3rings.co/resource/expens...
Chapters:
0:00 - Intro
0:15 - 1. Don’t repeat fields
2:56 - 2. Eliminate redundant work with linked records
7:06 - Use the base schema
9:12 - 3. Make good use of the primary field
11:56 - What to learn next

[@mollytt]

This was terrific. I appreciate a more advanced lesson and you delivered it perfectly. Thank you!

[@bobbinsew]

Great info! Thanks 🙏

[@mikescawen]

Thank you foe a very clear use of the junction table function along withe base inventory database. My question is probably a repeat but you have sold say Green shorts and yellow shorts but as we all know we need to stock say same, medium and large sizes of all our clothing products. Where dry start with Green shorts that are small, medium and large? Thank you. Mike

[@Nutrisof]

Nice video Julian, but the base can be better to avoid issues down the line.
Friendly, constructive advice :)
...
What if you need to add more info about the movie itself? Cast, year, summary? You cannot do it in that table becase the entity (table) is reviews, so the attributes (columns) must talk about the entity.
For that, make a separate table, call it "movies", list all the movies and add all the attributes you want about the entity ("movies" now), don't forget to create a primary key.
Then list that table back to the "reviews" table in a one:many relationship*, and have the primary field be a concatenation of the foreign key (movie's primary key) and a sequence number (like autonumber**), and then write the reviews as you wish.
*It's a one-to-many relationship, because you could want to have 2 or 20 reviews about the same movie overtime, and with this structure you can do it. And even more, visualize the reviews you have per movie right in the movies table, and even do calculations on that (like counting the reviews per movie) using rollup on that linked record.
**Using autonumber in your formula instead of dateTime (or created time) is better because it'll keep track of each row's sequence no matter what, while... if you still want to use dateTime and if you want to import many rows at the same time, they'll have the same exact date, and if you're importing 2 or more reviews of the same movie... the formula will show the same movie titile and same dateTime, and that's a problem.
So to recap: make movies be a separate table, and improve the primary field.
Have a great day :)

[@SriKala]

Love these videos Julian!

[@julian_post]

Thank you Sri!! Hope you're doing well

[@PM-st6vu]

this was a great summary, thank you!

[@julian_post]

Welcome!

[@ladytezt]

I have a complex base I really need to tidy up. Thanks for the Base schema suggestion!

[@julian_post]

Welcome! Happy tidying :)

[@mikescawen]

Obviously I didn't spell check! So sam e is small, do we start instead of dry

[@jenniferushie1374]

Too fast for a beginner 😢😢

[@julian_post]

Thx for the feedback