I have a Base with below:
- Table A = Collections
- Table B = Projects
- Table C = Dept 1 Sub Tasks
- Table D = Dept 2 Sub Tasks
- Table E = Dept 3 Sub Tasks
- Table F = Dept 4 Sub Tasks
We create Projects and Collections, with Linked Records.
When a Project is added, it then links to all the different table sub tasks. These are very different based on departmental needs, hence the different tables.
I need to have a direct link between each sub task and their respective collections so that I can run High level meetings accessing each departments status/info in an Interface with ability to change data. This means an interface run from Table A with grid views inserted for each table A, B, C, D, E, F
Right now it works if I use a Collection lookup field on each subtask table to monitor for changes, and then an automation that then updates a sub task to a new linked record field connecting to the collection any time there is changes.
However as my base grows, and automations grow, I am concerned that there is a limit of 50 automations and without the ability to combine automations for lots of scenarios it creates lots of small one off automations.
Is there a way to use "Find Records" action, or something else, that only watches when a collection changes at Table B, to then find all subtasks of said project on each table and update those to the new collections as well ... all in a single automation run?
