Exactly!
There’s several Fibery limitations I’m trying to work around:
1a. Not having any way to have filtering/conditional logic when auto-linking
1b. Not being able to auto-link using many-to-many fields
2a. Not having formulas in filters. Specifically automation filters in this case.
2b. Not having branching logic in automation rules.
Maybe if I knew how to script things, it would make things easier for me, but I don’t so I have to rely on more traditional methods like formulas and automations which get very exhaustive to build and maintain.
Here’s a common scenario that we struggle to handle without having many, many separate automations that can be complex and sometimes unreliable. Using a self referencing field, I’ve been able to simplify everything into a single automation now, which is awesome, and now I’m trying to scale that approach to be able to streamline many other automations I have as well.
Relational Hierarchy:
[Iteration] M-M [Sprint]
[Iteration] M-M [Team]
[Team] 1-M [Sprint]
Ideal Logic:
WHEN
[Iteration].[Week Number] = [Sprint].[Week Number]
AND
[Iteration].[Year] = [Sprint].[Year]
AND
[Iteration].[Teams] is any of [Sprint].[Team] (Team A, for example)
LINK
[Iteration] to Team A’s [Sprint]
and if any of the conditions are no longer met, UNLINK the iteration from the sprint.
You helped me with a similar scenario in another thread before if it seems familiar Contains equivalent? - #12 by Chr1sG