
Grant_Davis1

5 - Automation Enthusiast
Comment Post Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
โMay 07, 2021
07:30 PM
Can synced tables be changed to allow syncing from within the same base?
Currently, creating a synced table does not allow syncing from a table in the same base. When only one source was allowed, this was reasonable, as creating a synced copy of a table in the same base doesnโt make sense. Now that you can have multiple sources, there are valid use-cases for this.
For example, the map app only lets you to work with one view, and I would like to visualize the addresses from multiple tables in one map. I can use multi-source synced tables create a single table for use by the map app, but this now must be in a separate base, due to the originally mentioned constraint.
See more ideas labeled with:
3 Comments