Cross-App Relationship v. Sync Table
I'm in the beginning stages of building a platform of applications for my company's facilities' managers. I've built an application named Facilities, which I will use as my master app. I'll have aroun...
Forum Discussion
Personally I never recommend the sync option because you cannot add any data to that table. I always, unless for a better reason, would recommend table-to-table relationships using Cross Application Relationships. Also you can send data back to the parent that way without issue.
When you build the cross-application relationship, you will set the access permission to the highest-level role to ensure that the connection and lookup fields work correctly.
I have many QuickBase customers using centralized-applications for storing centralized-data common across a business; and it is generally the smarter way to structure data to avoid a) duplication and b) bad data entry.
Syncing severely limits what you can do with the data in the synced table, and generally requires a higher level of knowledge for connecting data to the synced table. If you want to "replicate" a data table in an application so that you can set other characteristics and attributes to it; consider instead Table-to-Table relationship imports which can copy the data from your "master" source, but still provide you the flexibility of a customizable table.
When you build the cross-application relationship, you will set the access permission to the highest-level role to ensure that the connection and lookup fields work correctly.
I have many QuickBase customers using centralized-applications for storing centralized-data common across a business; and it is generally the smarter way to structure data to avoid a) duplication and b) bad data entry.
Syncing severely limits what you can do with the data in the synced table, and generally requires a higher level of knowledge for connecting data to the synced table. If you want to "replicate" a data table in an application so that you can set other characteristics and attributes to it; consider instead Table-to-Table relationship imports which can copy the data from your "master" source, but still provide you the flexibility of a customizable table.
Thank you! Having not used Sync tables in the past it's helpful to understand the limitations/complications. I will go the cross-app route. It's worked for me in the past. Thanks!