When to use 2 tables instead of 1 with AppSheet || AppSheet Explained
When you're designing an app, and you want to have a single point of data-entry for your users - if you've split your reference data into multiple tables, it can be difficult to maintain this "single data-entry" interface.
One thing you can do to make this easier, is to combine your two tables into one - adding in conditional sections for the different "types" of records that can be created in that table.
So instead of having 2 tables, one for each separate type of record
You instead have 1 table, with multiple records of different types
The key is to include a column that differentiates the "type" of record
----| Table of Contents |----
0:00 - Intro
1:23 - Two-Table Hierarchy Overview
2:02 - How to select from two-table options
3:53 - Combining two-tables into one
7:33 - How to tell when to combine tables into one
8:52 - Benefits of leaving things separate
10:17 - Ending
-----------------------------------------------------------------------------------------------------------------------
/////////////////////////////////////////////////////////////////////////////
/// SUPPORT THE CHANNEL
/////////////////////////////////////////////////////////////////////////////
//
// Schedule a 1-on-1
// https://calendly.com/multitechvisions...
//
// Patreon
// / multitech
//
// 15% off @ https://www.AppSheetTraining.com
// Code: MULTITECH-15
//
// Tip Jar
// https://www.MultiTechVisions.com/Tips
//
//
/////////////////////////////////////////////////////////////////////////
For more information about MultiTech Visions, visit
https://www.MultiTechVisions.com
#CitizenDeveloper #AppSheet #Patreon