[UPDATE: the goal is actually to have an easy way to trigger an automation when entities of various databases are linked, without multiplication of automations or complicated scripts.]
A very common automation needed, yet as far as I know, a linked entity cannot be ‘updated’ without affecting existing linked entities, by an automation action without a script.
I mean ‘updated’ without affecting existing linked Tasks (I updated the post above, thanks)
E.g. When a task is linked to a team, the “owner” user field is set to the team lead.
If a Task has only one parent Team, then add an automation to the Task database, not in the Team database. In my case, a task can have multiple parent teams however.
The second workaround I used, requires a ‘target entity’ to-one helper field in the Team database.
In the exaple above, it would be ‘TargetTask’.
The step result variable [Step 1 linked Task] then can be used to set the TargetTask,
and a second action then updates that TargetTask.
This complicates the schema however, so I rather find a more efficient solution.
Sorry this is actually not true. A task can be updated using the [Step 1 linked Team].
My actual goal in this topics is to simplify automations when a task is linked to a number (30+) parent databases without complicated scripts or multiplication of automations. I guess that without polymorphic relations this cannot be simplified. So I may need to update the title of this topic.
Indeed, because automations are db-specific, if you need an action to execute for the ‘entity linked to…’ events across multiple relations, then you need multiple automations.