Hello there! Is it possible to put multiple data points from various tables into a single table via Cross Doc pack? I’ll give an example: Table 1, Doc 1 - To Do at Home: Project - Pick Apples | Due Date - 6/12/20 | Notes - Only pick ripe ones! Table 2, Doc 2 - To Buy: Project - Buy Ladder | Due…

@Benn_Bennett @John_Beaudoin_Jack , @ABp , @Bill_French et al — I’m about to launch a custom pack just for this! [image] Preview: Cross-doc Plus (codenamed) — My opinionated take on Cross-doc Making Packs If I could build just one pack in my lifetime, it would be this. Alm…

[image] Benn_Bennett: put multiple data points from various tables into a single table via Cross Doc pack? No. That’s not the [apparent] intended function of Cross Doc. What you’re describing is Merge Docs and that hasn’t been invented yet although there are some similar mentions scattered i…

@Bill_French is right in that Cross-doc doesn’t lend itself well to a “many to one” solution. Its best used in a “one to many” setup. There are some workarounds if you want to sync in tables from those other docs, then run an automation to add the new rows to a combined table. It might become pretty…

Would it be possible, in my previous example, to merge elements of various tables into one? I’m trying to NOT have a very large table with various blank cells and instead have multiple tables with a few common elements (columns) and some unique to each case. I guess I’m still trying to figure out d…

The solution would be to sync tables from other docs into that one core doc you’re talking about. Then you would create a new table in the core doc, and buttons or automations from the others that would copy the rows into it. This would create you one core table to work from, but it would be disconn…

I’m sorry, I was just re-reading my comment and realize I wasn’t clear. Would it be possible if ALL tables were in the same doc to somehow merge various columns from separate docs into a separate table? For my (actual) example, I have clients at various sites, with each site containing various elem…

It sounds like all you need is the basic table and then views of that table that show only the info relating to certain values (like demographics) - all in a table and then you make new views in different section dividing it up to see the best of both worlds - in your words, one large table with so…

[image] Benn_Bennett: Does it make more sense, in terms of database design, do have one large table where certain cells are blank, or to have 2 tables where all cells are filled in? [image] Tony_Creech: It sounds like all you need is the basic table and then views of that table that show …

@Benn_Bennett Your use case is pretty similar to my pet project in Coda. I once used the “one doc to rule them all” approach which consisted of a mega-table of tasks and milestones, organized by project specific views, or context-specific views, in separate sections and folders of the document. The …

[image] John_Beaudoin_Jack: But I’ve lobbied for a Todoist Pack that would make the Zapier recipes unnecessary. Yep - totally agree, but it appears you carefully identified the feature gap and applied a best-available-case to get the automation functional. While I’m not a big fan of code-free…

Absolutely on the open pack architecture!

Cross-Doc Into Single Table?

Paul_Danyliuk April 28, 2022, 8:51pm 14

@Benn_Bennett @John_Beaudoin_Jack, @ABp, @Bill_French et al — I’m about to launch a custom pack just for this!

Topic		Replies	Views
Connections via Lookup & Filter lost using cross-doc	7	3129	June 2, 2021
"All my tasks" view -- only possible with a "one big table" of tasks across all projects?	7	912	March 25, 2024
Help! How to share filtered views involving multiple tables via cross-doc	23	1820	March 14, 2023
Extract a Table to another doc Making Packs	4	730	November 28, 2020
Is there a way to connect 2 CODA documents?	32	9120	October 9, 2019

Cross-Doc Into Single Table?

Related topics