Hi Julian. I’m brand new to Airtable. I’m building a CRM for a consulting business. We have three types of people I need housed in the database: Clients, Prospects and Center of Influences. Each of these have different information needed to be captured. Would you put them in one table with a field for record type or would they each be their own table?
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
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 :)
![Hands-On Power BI Tutorial 📊 Beginner to Pro [Full Course] 2023 Edition⚡](http://i.ytimg.com/vi/77jIzgvCIYY/mqdefault.jpg)
![Hands-On Power BI Tutorial 📊 Beginner to Pro [Full Course] 2023 Edition⚡](/img/tr.png)
Hi Julian. I’m brand new to Airtable. I’m building a CRM for a consulting business. We have three types of people I need housed in the database: Clients, Prospects and Center of Influences. Each of these have different information needed to be captured. Would you put them in one table with a field for record type or would they each be their own table?
This was terrific. I appreciate a more advanced lesson and you delivered it perfectly. Thank you!
Wohoo! Thanks for letting me know @mollytt !
I have a complex base I really need to tidy up. Thanks for the Base schema suggestion!
Welcome! Happy tidying :)
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
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 :)
Great info! Thanks 🙏
this was a great summary, thank you!
Welcome!
Love these videos Julian!
Thank you Sri!! Hope you're doing well
Obviously I didn't spell check! So sam e is small, do we start instead of dry
Too fast for a beginner 😢😢
Thx for the feedback