View all my tasks

Welcome to the community, @Rob_Warner! :slightly_smiling_face:

It doesn’t sound like your database is setup in the appropriate way.

Instead of having a different tab (i.e. table) for each one of your project categories, your projects should all be in ONE TAB with a single-select field called “Category”.

Then, you can easily do what you would like to do in many different ways.

Hope this helps! If this answers your question, could you please mark this comment as the solution to your question? This will help other people who have a similar question. :slightly_smiling_face: If not, please let me know what else you need help with!

Thanks, ScottWorld, but that doesn’t work for us. We need separate tabs because each tab has a unique workflow that we can’t smash into one tab. Let me know if you have any other ideas!

This is a tricky situation indeed. The collaborator field is great because it helps to notify collaborators about records assigned to them, but as you’ve seen, it doesn’t create an easy way to see all records across multiple tables for a single person.

My gut says to add a [Collaborators] table to store collaborator data, and link projects to their respective collaborators from the other tables. The benefit is that you can then create a view for each collaborator (assuming it’s a relatively manageable number), where each person can see links to all of their projects across all tables. The downside is that you’ve already got an Airtable collaborator field in your project type tables, so this adds redundant data.

I’m currently a team of one, and haven’t used Airtable’s collaborator features before, so I’m not sure if there’s a clean way to get the best of both worlds.

That was my instinct as well! The only issue is that you can’t create such a table :weary: As far as I can tell at least. Presumably you’d make the primary field collaborator and then pull in all the projects, right? But the primary field can’t be a collaborator nor can it be reference to another table…the plot thickens!

True, but we don’t need the primary field to be a link to another table. We need other tables to link to the records in this [Collaborators] table. After building the links, Airtable will automatically add reciprocal fields in [Collaborators] showing the incoming links from the other tables (one new field per linking table).

Airtable is pretty slick about field conversion, especially when it comes to turning an existing field into a link to another table. My gut says that you might be able to convert a collaborator field to a link field. If Airtable does the same thing that it does with other similar conversions, it will add records to the target table matching the collaborator names.

You might run a test of this in a dummy base for starters. Make a table with a collaborator field, putting yourself (and maybe one other collaborator, if they’re willing to be a guinea pig) as the collaborators on a handful of dummy records. Make a new [Collaborators] table, and delete all of the empty sample records. Back in your first table, edit the collaborator field settings to change it to a link to the new [Collaborators] table, and see if it auto-adds records matching the existing collaborator entries.

Ah I see what you’re saying. That took me a while to comprehend :slightly_smiling_face:

I think the issue with that set up is that currently I really like the way collaborators behaves, specifically when it notifies folks who’ve been added to records. In your solution is there a way to keep that ability?

Right. That feels a little weighty for what should be a simple view. I’ve just created views in each of the tabs that filters those person’s projects and I think that’s what I’m gonna go with. Thanks for your help though!

Glad to know that you got something working, even if it’s not the ideal solution! If you would, please mark the appropriate comment above as the solution to your question. This helps others who may be searching with similar questions. Thanks!

@Rob_Warner, wondering if you've made more progress on this issue? Idk if Airtable had Multi-source syncing back in June 2020, but it might be something you can use (https://support.airtable.com/docs/multi-source-syncing). I don't like the idea of having to go to a different Base, but you can create a Synced table in the new Base and then add data (which comes in as additional records) from multiple tables in your original Base. You can choose what fields to bring in from each source/table. So you would maybe bring in Owner and Status for example. 

Bonus: just noticed that you can then go your first Base, and create a Synced table and source it from the new Multi-source table in the new Base!! 

Please let me know if this makes sense, or if, since 2020, you've found a better/different work around! 

Why doesn't Airtable have a simple "Summary by User" button/table/view/extension!!? Beats me!