Many people, including myself, have endeavored to create a 2-way live and editable sync between coda tables in different documents.
The solutions presented previously, including by myself, have many fatal flaws:
They require mapping of columns manually. So if you have a 100 column table, you have to map 100 columns.
They require setups of webhooks to RECEIVE the 2 way sync request which both more work on the user to set up AND must be updated everytime columns change
Its not scalable. When a user wants to ADD even a single column to their table, they must then update the actual button that maps column data over AND the webhook automation that catches that information in the second document
ENTER THE SOLUTION
I’ve created a pack that allows you to create an automatic 2 way live-sync between 2 coda tables in different documents AND:
NO MAPPING OF COLUMNS
Simply provide the pack a few bits of information such as the URLs to both Coda documents, the target table names to sync, and ID columns
This makes syncing even tables with 100s of columns a breeze
INSTANT UPDATES
Need to add new columns to your tables? No biggie! The pack takes care of the logic, recognizes the newly added columns, and updates accordingly
Hi, then if I well understand…
The need of this kind of pack just reveal the impossible feature of just having “pointers” to an existing “object” of type “table” or “database”…
Then you needed to “sync” an existing database to another one duplicating everything???
Let’s say you have a database of 100 000 images in a “Doc” and want to access with read or write access then, by now, you only could do it duplicating it???
¿¿¿¿I am wrong isnt’it ??? ¿?¿¿¿???¿¿???
Isn’t it ?!