Aggregating Multiple Tables with relational relationships

[Peter_Spencer]

Dear Sir or Madam,

Could I have assistance in aggregating two distinct tables (activity and maintenance activity) in one aggregate table listing all activities, given they use the same parameters? The page in question here

So far, I’ve tried a relational lookup and looking at other community messages without success.

Aggregate Table (Pivot)

I’d like to aggregate a table into a view that only includes the grouped columns and the summed column. For example everyone has hours they add each day by task and I’d like to create a view that is only the total hours a user worked by task like this example. [image] While I can group the table I can’t have the individual day/hour rows. What’s the best way to do this? Thanks in advance!

Aggregating rows from multiple databases

Hello there! Before asking for help with my problem, let me give some context: CONTEXT I manage a team of 20+ people where each person works in specific projects independently. I’ve been exploring Coda as replacement of the project management tool that we are currently using to organise (store files, docs, notes) and keep track (status, deadlines, resources) of our projects. I was able to implement - and even improve - pretty much everything that we need in such a tool in order to make this…

Could you advise if aggregation is something Coda can do?

Secondly, could you advise why the conditional sum aggregation formula is within Tasks?

Activity.Filter(Tasks.In(thisRow.Tasks[Actual Hours]).sum())

Thanks in advance

[Mike_Ray]

I would solve this issue in a similar way to the answers in a related question you referenced here: Aggregating rows from multiple databases.

My suggestion is, generally, fewer tables are always better.

In your example, I would put Activity and Maintenance activity on one (1) table, especially since they have the same parameters/attributes/columns. Then filter the Activity Tasks from the Maintenance Activity Tasks where needed.

Then all other functions are easier to operate such as aggregating, math, etc.

While many new Coda users don’t like simplifying tables in their database construction, it does generally make your life easier. I’ve learned this the hard way with Coda. Build with database best practices and not necessarily how you might view/interact with the data.

If for whatever reason you must have two (2) separate Activity and Maintenance Activity tables, you could create a button and/or automation that adds/modifies entries from both tables to your Aggregated Table view table. So when a row is added/updated on either base tables, a row is added/updated on the Aggregated Table view table.

Another option is to use a Pack. One of the community members created a Pack that can do what you requested but it’s a little complex and does have some significant drawbacks, at least for my purposes, which is why I haven’t use it.

I don’t remember the name of the Pack so I can’t help you there, but I believe it was created by @Paul_Danyliuk and there’s a video demo. Please note that I could be wrong about who developed the pack.

Good luck!

[joost_mineur]

The pack mentioned by @Mike_Ray is probably:

Merge Table (Lite) Pack, extend Coda with Merge... - Coda

with this community post:

Launched: Merge Table Pack

The Merge Table pack enables merging and syncing multiple tables across docs into one combined sync table. Similar to the Cross-doc pack, but with the added benefit of being able to pull in rows from multiple tables at once to merge their values under common columns! Useful for combining multiple tables that share common columns, for example merging Tasks, Meetings, and Projects tables into a single Calendar layout table showing the names, type, and relevant dates for each. See the pack listin…