I cover the export feature towards the end of the video around the 5:15 timestamp, exporting shouldn't initiate a wizard as it only exports to a CSV file. Only the import feature requires the wizard to map the data.
question. Do you recommend one large base with dozens of tables (say as many as 100) or should the tables get broken out into smaller bases? And can data from one table be easily used in another base? Example if I'm tracking tech tips by many different gurus (such as you! LOL) If one has a database of Guru's can a database of schemas have a row (field) with a drop down list that draws it's selected list to choose from being dynamically related to the gurus in the other base?
Great question! It really depends on how you want to segment the data and what data needs to be limited if shared (which can benefit from having multiple bases). The advantage of multiple bases is making the data more manageable instead of having 100 tables. If there’s a common theme across tables then it may make sense to create a separate base for it. You can link and sync up bases which I’ve made a video on. You can make a dynamic drop down base on a table that is synced to an external base. For example you can limit the selection to a specific view let’s say “active gurus” where you created a custom view with the a status filter as “Active” and every time that table gets synced and updated it should make the drop down selection dynamic. I hope that makes sense, it’s always hard to explain things in this format as a comment 😂.
Very helpful feature to learn. thanks!
How can I export the interface into a PDF merging the PDF attached into the interface?
You’re good man.
Mine doesn’t have that wizard. What other way can I export my Airtable base to excel?
I cover the export feature towards the end of the video around the 5:15 timestamp, exporting shouldn't initiate a wizard as it only exports to a CSV file. Only the import feature requires the wizard to map the data.
question. Do you recommend one large base with dozens of tables (say as many as 100) or should the tables get broken out into smaller bases? And can data from one table be easily used in another base? Example if I'm tracking tech tips by many different gurus (such as you! LOL) If one has a database of Guru's can a database of schemas have a row (field) with a drop down list that draws it's selected list to choose from being dynamically related to the gurus in the other base?
Great question! It really depends on how you want to segment the data and what data needs to be limited if shared (which can benefit from having multiple bases). The advantage of multiple bases is making the data more manageable instead of having 100 tables. If there’s a common theme across tables then it may make sense to create a separate base for it. You can link and sync up bases which I’ve made a video on. You can make a dynamic drop down base on a table that is synced to an external base. For example you can limit the selection to a specific view let’s say “active gurus” where you created a custom view with the a status filter as “Active” and every time that table gets synced and updated it should make the drop down selection dynamic. I hope that makes sense, it’s always hard to explain things in this format as a comment 😂.
Btw here’s a link to my video on syncing tables - ua-cam.com/video/gnn5CJTDkMo/v-deo.htmlsi=h7rdrusbPz11KE_L